On Sep 2, 2014, at 9:06 AM, Gert Vanthienen <[email protected]> wrote:
> That way, people can choose which version of Karaf to use with Camel > 2.14.x. That would give people some extra time to migrate to the newer > version of Karaf if they need it - for the next minor version of Camel > (2.15.0), we should drop support for Karaf 2.3.x and only use Karaf > 2.4.x though to avoid we end up with an entire matrix of version > combinations to support/release. This would definitely need to be taken up with the Camel community, but it makes a lot of sense. CXF has already more or less dropped support for Karaf 2.3.x on master (CXF 3.1) so Camel will likely need to shortly as well. The main reason is due to Jetty. Trying to support Jetty 7.6.x (Karaf 2.3), Jetty 8 (Karaf 3.x), and Jetty 9 (hopefully Karaf 4, but needed for various standalone cases) is a HUGE HUGE pain due to the Jetty folks moving classes around all the time, changing class hierarchies, etc… CXF has dropped support for Jetty 7.x which means some use cases of Jetty within Karaf 2.3 will no longer work. I’m starting to look into the Jetty 9 support for Camel’s jetty components, but I’m kind of waiting for 2.14 to be out so we can look into dropping the 7.x support there as well. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
