TBH I'm not happy that we can't upgrade a micro version of a referenced library in a micro release of karaf. TBH I would rather prefer staying with 3.0.5 for the entire 2.x branch than keeping 2.3 for a micro dep upgrade.
In addition we should learn from this and completely remove all features from karaf. Even http, spring wrapper... Those should be maintained by the karaf team but not distributed in karaf core. They could be loaded from a cave repo or from any other method we've discussed in the last time. Because of this situation I think it is very important that we get rid of the problem in 3.0 for once and all. Knd regards Andreas On Sep 5, 2011 7:09 AM, "Jean-Baptiste Onofré" <[email protected]> wrote: > Hi all, > > as you have certainly seen, we have an issue with Karaf 2.2.3 and Camel. > In Karaf 2.2.3, we upgraded to Spring 3.0.6.RELEASE, whereas Camel still > uses Spring 3.0.5.RELEASE. > As Spring is major component for CXF, Camel, etc. So, we should > "address" a Spring update with a lot of attention. > > I propose: > - to rollback Spring to 3.0.5.RELEASE in Karaf 2.2.x. > - to create a Karaf 2.3.x branch, exactly a copy of 2.2.x, but with > update to Spring 3.0.6.RELEASE > - in both branches, we add all Spring features to cover all Spring > bundles. We have few issues to fix in both branches and I propose to > release 2.2.4 and 2.3.0 soon. > - update Karaf 3.0.x (trunk) to Spring 3.0.6.RELEASE > > WDYT ? > > Regards > JB > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
