Charles, I'm not sure I understand what the problem is. If you install a newer version of a JAR in the runtime, the jar file in the /system folder is not being used, e.g. if you install CXF 2.2.6 in a few weeks, the existing bundle in /system will still have the 2.2.5 version so it should not interfere as long as the versions on the import/export headers are ok. There might be an issue with things like custom namespace handlers and things like that though. E.g. for camel, the camel-blueprint work should make it easier to use multiple versions of camel using the XML syntax.
Actually, the only real solution is probably to have much shorter release cycles on the ServiceMix 4.x line, where we do a release quarterly or so to pick the latest and greatest bits of Camel, CXF, ActiveMQ, ... Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/12/14 Charles Moulliard <[email protected]>: > Excellent idea for SMX3 and SMX4. > > Concerning SMX 4.1 release, I propose that clarification is done for the > user concerning features and jars already installed in the distro (folder > system). The risk is that users using SMX4.1 wants in a near future to > install newer versions of Camel, PAX, CXF, ... and use features file to > install them. In this case, there will have a conflict with existing jars > provided in the distro (system folder). What is the procedure to follow to > be able to use these newer versions ? > > Regards, > > Charles Moulliard > Senior Enterprise Architect > Apache Camel Committer > > ***************************** > blog : http://cmoulliard.blogspot.com > twitter : http://twitter.com/cmoulliard > Linkedlin : http://www.linkedin.com/in/charlesmoulliard > > Apache Camel Group : > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm > > > On Mon, Dec 14, 2009 at 8:54 AM, Jean-Baptiste Onofre > <[email protected]>wrote: > >> Hi gentlemen, >> >> Yesterday I have upgraded SMX resources (component, feature, etc) to use >> Apache Camel 2.1 as it has been released. >> >> I think that we are not so far from a new SMX 3.3.2 and 4.1 release. >> >> I propose the following steps: >> >> 1/ I begin to prepare the 2009.02 components release. It includes: >> - component-pom 4 >> - jbi-maven-plugin 4.2 >> These artifacts will be submit to a first vote. >> - all components 2009.02 >> All components artifacts will be submit to a second vote. >> >> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using >> Karaf 1.2.0 and perform some test to check how it runs. >> >> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the smx >> 3 and smx 4 POMs to use the previously released components. >> Two votes will be submitted: one for SMX3 and another one for SMX4. >> >> What do you think about that ? >> >> Regards >> JB >> >
