Use a separate version for jolokia so we can use productized build of jolokia #503
Conversation
This file contains 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
mcarlett
approved these changes
Jan 24, 2025
Croway
approved these changes
Jan 24, 2025
cunningt
merged commit 5ca99c0
into
jboss-fuse:camel-spring-boot-4.8.3-branch
2 checks passed
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.
jolokia-version from camel-parent is unused in the productized camel build because camel-platform-http-jolokia is unsupported. camel-platform-http-jolokia is the only place where that version is used in a dependency or dependencymanagement entry so it's basically and orphaned version within camel.
In order to align to productized jolokia within camel-spring-boot, we should add a separate jolokia version within c-s-b - the dependency in camel-jolokia-starter will ensure that it gets aligned.