Repository navigation
ci: run the Camel apps of the integration tests on Java 25: JiraIT fails with them on 21 - #3094
Merged
Merged
Conversation
…ils with them on 21 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
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
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.
Follow-up to #3091, which links an installed JDK 21 into JBang so it no longer downloads one. With the Camel apps on Java 21,
JiraITfailed in all three runs of #3091 (3 of 3, "Action timeout ... Failed to receive message on endpoint: 'jiraServer.inbound'"), while the other 68 integration tests passed. It passed in the earlier runs where JBang had downloaded JDK 27 by itself (#3089 and #3090 at 16:38).This links JDK 25, the current LTS, instead of 21. The Maven build and the Citrus tests stay on 17. The integration tests on this PR are the check.
Why the Jira tests fail with the Camel app on 21 is being looked at separately. If the Jira Kamelets really don't work on Java 21, that's a bug for camel-jira rather than for this workflow.