We would need to upgrade Camel 2.17 to work with, at least, Karaf 3.x. The first version supporting JDK8. Ideally, we should upgrade to Karaf 4.0.0.
In fact, I think it already works with Karaf 4.0.0, but we need to state it officially. https://camel.apache.org/karaf.html As long as there are JDK8-supporting versions for all target environments of Camel (OSGi, servlet containers, JEE App Servers, etc.) and we are compatible with their "JDK8 and up" versions, I'm all for it. We really need to make Processors, Aggregation Strategies, etc. @FunctionalInterfaces. *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani Blog: raul.io | twitter: @raulvk <https://twitter.com/raulvk> On Thu, Jan 28, 2016 at 2:35 PM, Daniel Kulp <dk...@apache.org> wrote: > > For master (targeting 2.17), I see we’re still setup for Java7. Would > it make sense to move to requiring Java8? We can certainly start taking > advantage of the new things in Java8, but there are also dependencies (like > Jetty) that now require Java8 and more and more of them will be requiring > that. (example: CXF 3.2 will be Java8 only as well) > > It sometimes makes back merging fixes to 2.16/2.15 tricky if you use Java8 > features, but that’s going to be a problem eventually anyway. > > Thoughts? > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > >
