Remove hardcoded camel / camel-kamelets versions from citrus-application.properties#2815
Merged
Conversation
…ion.properties and ensure that the camel and camel-kamelets versions are kept in line with the current state of the project (use maven's ${camel.version} and ${project.version}
oscerd
approved these changes
May 1, 2026
Contributor
Author
|
From the CI logs - this is working -
|
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
2 participants
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.
Starting to work through the integration test failures - there seem to be multiple issues and I think it makes sense to handle them one by one.
The citrus-application.properties file being used contains hardcoded versions of kamelets and camel - we want it to use the versions for testing that are defined in the camel-kamelets pom.xml - so for kamelets, we'd like
${project.version}and for camel we would like${camel.version}. Make this file a filtered testResource and ensure that the rest of src/test/resources remain unfiltered.Log the values of citrus.camel.jbang.version and citrus.camel.jbang.kamelets.version to ensure that this fix works in the integration tests.
I expect that after this PR integration tests will still fail as there are other issues (will be handled in separate PRs)