P-Alban, Stefan:
Thank you. That is helpful.
P-Alban: Can you elaborate on "You can just force all the dependencies to a
released version of camel to have only your component in an upper version."?
How do you force up one component version without creating conflicts with
camel-package-mave
Is there a best practice for bumping the version of a single component when
testing a new patch/feature?
I would like to be able to build and test the single component without
changing the entire version of the camel tree.
Right now, if I add a version element to a component sub-pom (say
2.16.1-m
