Hi, You can just force all the dependencies to a released version of camel to have only your component in an upper version. I could not work if your component relies on new features of camel core.
Best regards P-Alban Pierre-Alban DEWITTE @padewitte +33 6 59 55 64 59 On Wed, Jan 13, 2016 at 8:24 AM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi, > > This depends on what you are intending to do with the change. If you just > want to do *test* the new feature with a released version you might build > the version locally without changing the version at all. Obviously you > cannot push that to any nexus or send it to anybody else without causing > major confusion. > If you actually want to create a patched version of one component, you > will have to change the version of the whole camel project to e.g. > 2.16.1-mypatch-01 and build everything with that version. In the delivery > you can mix the patched bundle with the original ones (so you have version > 2.16.1 for most of your jars, just the patched one is on > 2.16.1-mypatch-01). Changing the version for the whole camel tree can be > done with the maven versions plugin (you really don't want to touch each > pom in the whole camel tree manually). The build of the whole thing will > take some time. > > Best regards > Stephan > > -----Original Message----- > From: Doug Tung [mailto:dwt...@isg.la] > Sent: Mittwoch, 13. Januar 2016 05:25 > To: dev@camel.apache.org > Subject: Changing a single component version > > 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-myVersion, I start having build errors because the version is > automatically applied to camel-package-maven-plugin, camel-test-spring and > perhaps others. > > Any advice is appreciated. > > Doug > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Changing-a-single-component-version-tp5776189.html > Sent from the Camel Development mailing list archive at Nabble.com. >
