Yes, it makes sense. BTW, It could be connivence for the people to know which version of camel-extra works for the patch release version of camel. -- Willem Jiang
Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Monday, January 21, 2013 at 3:05 AM, Henryk Konsek wrote: > > I dont think we need to fix camel-extra at every matching ASF Camel release. > > There is a camel-extra 2.10.0 release and that is fine IMHO. > > > > Actually I would vote for syncing *all* releases of Extra Camel with > ASF Camel. The pros are as follows: > a) It is more intuitive for end-users to use single Camel version in > theirs POMs. > b) We guarantee users that the the latest Camel Extra has been tested > against the latest ASF Camel. > > > The next could just be the 2.11.0 which has the OSGi features XML file. > > So we introduce the OSGi features in the 2.11 onwards. > > > > Yes, I plan to add full-blown OSGI support for Camel Extra since the > version 2.11. > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com
