Claus, Thanks for the heads up! That are the usual kinds of mismatches we run into when we start integrating the NMR and Features kit. In order to become more agile in picking up new versions of dependencies, we should move to using OBR in the near future. I've just raised https://issues.apache.org/activemq/browse/SMX4-654 to get that fixed as soon as possible once the 4.3.0 release has been cut.
Regards, Gert Vanthienen ------------------------ Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Thu, Oct 28, 2010 at 2:54 PM, Claus Ibsen <[email protected]> wrote: > On Thu, Oct 28, 2010 at 2:48 PM, Gert Vanthienen > <[email protected]> wrote: >> L.S., >> >> Now that the release of Camel is due to go out any day now and >> Jean-Baptiste is already working on getting that into ServiceMix, we >> should get ourselves ready to do a follow-up Apache ServiceMix 4.3.0 >> release. I'll create set of JIRA issues for the release process and >> use JIRA links to point out the dependencies between the different >> builds. >> > > Just a note. We should align the Spring version used in Camel features > and SMX features. > I had some trouble with Camel 2.5 using Spring 3.0.4 and Karaf 2.1 using > 3.0.3. > So would be good to let SMX use Spring 3.0.4. > > >> If anyone has some cycles available, it would be good if we could do >> some builds locally to ensure that the kits are OK (no duplicate >> bundles, servicemix starting clean without warnings/errors, examples >> working fine, ...) before we actually start releasing things. The >> more things we can catch at this point in time, the easier the actual >> release builds and votes will go. >> >> Thanks, >> >> Gert Vanthienen >> ------------------------ >> Web: http://fusesource.com >> Blog: http://gertvanthienen.blogspot.com/ >> > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: [email protected] > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ >
