Repository navigation
ci: give JBang the Java 21 the Camel launcher needs, and keep the integration tests on 17 - #3091
Merged
Merged
Conversation
…her needs The tests run jbang camel@apache/camel, whose launcher declares //JAVA 21+ since CAMEL-23112. With JDK 17 set up, JBang 0.142.0 fails with "No suitable JDK was found for requested version: 21". The Maven builds stay on 17: Camel is still compiled for Java 17. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
…s out on 21 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
davsclaus
changed the title
…etup-java installs Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
davsclaus
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Claude Code on behalf of Claus Ibsen.
The Integration Tests workflow sometimes fails in "Run Tests" before any test runs:
The step runs
jbang camel@apache/camel. Camel's JBang launcher has declared//JAVA 21+since CAMEL-23112. With only JDK 17 set up, JBang has to download a JDK 21, and that download fails now and then. It passed on #3089 and #3090 at 16:38, and failed on #3090 at 16:07 and on #3093 at 17:53 and again at 18:35.The first version of this PR switched the workflow to Java 21. Then
JiraITfailed twice in a row (3 of 3, "Action timeout ... Failed to receive message on endpoint: 'jiraServer.inbound'"), while every other integration test passed. JiraIT passes on 17.So this sets up both JDKs, with 17 as the default (listed last) for the Maven build and the Citrus tests. JBang doesn't look at the JDKs
setup-javainstalls: with both installed it still failed with the same error, althoughJAVA_HOME_21_X64was set. So the step links that one into JBang withjbang jdk install 21 "$JAVA_HOME_21_X64", and JBang no longer downloads a JDK at all.The integration tests on this PR are the check.