camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Cosentino <ancosen1...@yahoo.com.INVALID>
Subject Re: [DISCUSS] Move to java 8 for 2.17?
Date Thu, 28 Jan 2016 14:47:42 GMT
I think it's time to start the switch, because many of our clients, libs etc. are already on
Java8.

I don't think it will be easy to have a stable codebase immediately.

 --
Andrea Cosentino 
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, January 28, 2016 3:43 PM, David Karlsen <davidkarlsen@gmail.com> wrote:
+1

So much goodness of lambdas and methodrefs which will make things a lot
smoother and you have a very good point about thirdparties. And even with 9
being a bit set back it's still in reach so moving to 8 seems sensible
28. jan. 2016 15:35 skrev "Daniel Kulp" <dkulp@apache.org>:


>
> 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
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>

Mime
View raw message