Re: Changing a single component version

2016-01-13 Thread Doug Tung
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

Re: Changing a single component version

2016-01-13 Thread Dewitte Pierre-Alban
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:2

RE: Changing a single component version

2016-01-12 Thread Siano, Stephan
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