Roadmap for Apache Camel 2.18 and towards Camel 3

The Apache Camel roadmap to 2.18 will not include support for Java 1.7. The community is being proactive to help users prepare for the change using its communication channels.

Claus Ibsen

Apr. 06, 16 · Integration Zone · News

Like (4)

Save

4.05K Views

the camel team recently announced that camel 2.17 would be the last release to support java 1.7. and that the following release camel 2.18 will require java 1.8.

the numbers in the versions aligns very well to make it easy to remember:

camel 2.17 = java 1.7
camel 2.18 = java 1.8

so with java 1.8 being the minimum java version and that the code is compiled as 1.8 source brings in all the glory of java 1.8 with aspects from functional programming with lambdas and whatnot.

apache camel has a huge community of existing camel users, and we do not want to throw you guys under the bus, with massive java 1.8 api changes in apache camel 2.18. instead we see this release as a stepping stone towards more java 1.8 readiness and the next major release camel 3.0.

we have put up an open discussion in the camel community on the developer mailing list, where you can read and participate. we love to hear feedback from the community.

you can read online using nabble where you can also post to the list. or you can signup using old fashioned mailing list and write emails.

but what if you want to provide feedback elsewhere. well i am sorry but apache software foundation mandates openness and transparency. the discussions about the apache camel project must take place using asf infrastructure such as the mailing list. however you are welcome to post a short comment on this blog, and i can post your comments on the mailing list on your behalf, if you are not arsed to signup on a mailing list, or register using nabble. however you do yourself a favor of signing up the camel mailing list as there is a ton of information you can learn from other camel users.

just a word about camel 3.0. the big goal for camel 3.0 is less technical but more a new website and new documentation. and we would love to see a new project logo as well. the technical parts are sure there too, but its overdue for a modern website with documentation we maintain from the source code so its much easier and faster to keep it up to date. also all the eip and component options is slurped from the source code to ensure the documentation is 100% in sync.