You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Andrew Kennedy <an...@cloudsoftcorp.com> on 2015/02/10 22:14:01 UTC
Java Seven and Eight
Hi.
What is our current policy for Java 1.7.x and 1.8.x usage? I see that there
have been some recent PRs that changed to use the proper Java `javac`
compiler instead of Groovy, and some references to fixing build errors with
java 8 as well.
Can (Should?) we be using JVM and JDK 7 features in the code now? What
about lambdas and other JVM 8 features? I had an ideafrom somewhere that
we are restricted to Java 6, perhaps for some reason to do with jclouds?
But, that doesn't seem right...
FYI, based on Oracle documentation [1] Java 6 'End of Public Updates' was
February 201, and for 7 it is April 2015. Their 'Premier Support' for Java
6 will end on December 2015, and July 2019 for 7. We're good until March of
2022 for 8, with 'Extended Support' for that lasting until 2025!
[1] http://www.oracle.com/technetwork/java/eol-135779.html
Cheers,
Andrew.
--
-- andrew kennedy ? distributed systems hacker :
http://blog.abstractvisitorpattern.co.uk/ ;
Re: Java Seven and Eight
Posted by Svetoslav Neykov <sv...@cloudsoftcorp.com>.
When discussing support for Java versions, keep in mind that there are users relying on alternative implementations, most notably IBM Java. Version 8 is still in beta, while version 6 will be supported for almost 3 more years - http://www.ibm.com/developerworks/java/jdk/lifecycle/ <http://www.ibm.com/developerworks/java/jdk/lifecycle/>.
Svet.
> On 11.02.2015 г., at 14:16, Andrew Kennedy <an...@cloudsoftcorp.com> wrote:
>
> I'd just like access to these Java 7 features, in no particular order.
> Although try-with-resources is probably most immediately useful.
>
> - New IO classes
> - Try with resources
> - Diamond notation for generics
> - Multi-exception catch clauses
>
> This would make us incompatible with Java 6 JREs, obviously. Is this such a
> bad thing
>
> I would need to investigate further to find out what sort of enterprise
> support is available for Java 7 runtimes, and of course whether it would
> harm adoption of Brooklyn. However we should be bearing in mind the types
> of enterprise that are likely to be open to adopting Brooklyn (and
> associated technologies like Cloud provisioning, Docker and Clocker, modern
> NoSQL stores, Software-Defined Networking and NFV, et cetera) in the first
> place are going to be forward looking rather than conservative, and would
> therefore be likely to be using the latest cutting edge JVMs. Anyone with
> actual useful data or even just anecdotes please jump in here...! Also of
> note is that Java 7 went GA in 2011, with previews even earlier, so that's
> four years plus of availability now.
>
> Andrew.
>
> --
> -- andrew kennedy ? distributed systems hacker :
> http://blog.abstractvisitorpattern.co.uk/ ;
>
> On 11 February 2015 at 00:05, Aled Sage <al...@cloudsoftcorp.com> wrote:
>
>> Hi Andrew,
>>
>> To-date, Brooklyn supports Java 1.6 and 1.7. It probably (?) supports 1.8
>> - I'm not sure if enough QA has been done on that yet.
>>
>> Could folk who are using Java 8 shout out to let us know how that's
>> working out?
>>
>> ---
>> For dropping 1.6 support, jclouds talked about doing that when they
>> release 2.0.0 I think. I don't think there's a timeframe for that yet. When
>> jclouds drop support, then we'll definitely do so (if we haven't already).
>>
>> We've talked to a few enterprise users who have all been fine with
>> dropping 1.6 support, but we haven't talked to enough of them or looked for
>> feedback on the mailing list yet. If there is a big benefit, then we could
>> discuss doing that - for after 0.7.0 is released so we can warn people that
>> 0.7.0 will be the last release supporting java 1.6?
>>
>> We should keep supporting 1.7 for the foreseeable future (at least until
>> the majority of enterprises have switched to Java 8). So no JVM 8 features
>> in Brooklyn unfortunately.
>>
>> Aled
>>
>>
>>
>> On 10/02/2015 21:14, Andrew Kennedy wrote:
>>
>>> Hi.
>>>
>>> What is our current policy for Java 1.7.x and 1.8.x usage? I see that
>>> there
>>> have been some recent PRs that changed to use the proper Java `javac`
>>> compiler instead of Groovy, and some references to fixing build errors
>>> with
>>> java 8 as well.
>>>
>>> Can (Should?) we be using JVM and JDK 7 features in the code now? What
>>> about lambdas and other JVM 8 features? I had an ideafrom somewhere that
>>> we are restricted to Java 6, perhaps for some reason to do with jclouds?
>>> But, that doesn't seem right...
>>>
>>> FYI, based on Oracle documentation [1] Java 6 'End of Public Updates' was
>>> February 201, and for 7 it is April 2015. Their 'Premier Support' for Java
>>> 6 will end on December 2015, and July 2019 for 7. We're good until March
>>> of
>>> 2022 for 8, with 'Extended Support' for that lasting until 2025!
>>>
>>> [1] http://www.oracle.com/technetwork/java/eol-135779.html
>>>
>>> Cheers,
>>> Andrew.
>>> --
>>> -- andrew kennedy ? distributed systems hacker :
>>> http://blog.abstractvisitorpattern.co.uk/ ;
>>>
>>>
>>
Re: Java Seven and Eight
Posted by Andrew Kennedy <an...@cloudsoftcorp.com>.
I'd just like access to these Java 7 features, in no particular order.
Although try-with-resources is probably most immediately useful.
- New IO classes
- Try with resources
- Diamond notation for generics
- Multi-exception catch clauses
This would make us incompatible with Java 6 JREs, obviously. Is this such a
bad thing
I would need to investigate further to find out what sort of enterprise
support is available for Java 7 runtimes, and of course whether it would
harm adoption of Brooklyn. However we should be bearing in mind the types
of enterprise that are likely to be open to adopting Brooklyn (and
associated technologies like Cloud provisioning, Docker and Clocker, modern
NoSQL stores, Software-Defined Networking and NFV, et cetera) in the first
place are going to be forward looking rather than conservative, and would
therefore be likely to be using the latest cutting edge JVMs. Anyone with
actual useful data or even just anecdotes please jump in here...! Also of
note is that Java 7 went GA in 2011, with previews even earlier, so that's
four years plus of availability now.
Andrew.
--
-- andrew kennedy ? distributed systems hacker :
http://blog.abstractvisitorpattern.co.uk/ ;
On 11 February 2015 at 00:05, Aled Sage <al...@cloudsoftcorp.com> wrote:
> Hi Andrew,
>
> To-date, Brooklyn supports Java 1.6 and 1.7. It probably (?) supports 1.8
> - I'm not sure if enough QA has been done on that yet.
>
> Could folk who are using Java 8 shout out to let us know how that's
> working out?
>
> ---
> For dropping 1.6 support, jclouds talked about doing that when they
> release 2.0.0 I think. I don't think there's a timeframe for that yet. When
> jclouds drop support, then we'll definitely do so (if we haven't already).
>
> We've talked to a few enterprise users who have all been fine with
> dropping 1.6 support, but we haven't talked to enough of them or looked for
> feedback on the mailing list yet. If there is a big benefit, then we could
> discuss doing that - for after 0.7.0 is released so we can warn people that
> 0.7.0 will be the last release supporting java 1.6?
>
> We should keep supporting 1.7 for the foreseeable future (at least until
> the majority of enterprises have switched to Java 8). So no JVM 8 features
> in Brooklyn unfortunately.
>
> Aled
>
>
>
> On 10/02/2015 21:14, Andrew Kennedy wrote:
>
>> Hi.
>>
>> What is our current policy for Java 1.7.x and 1.8.x usage? I see that
>> there
>> have been some recent PRs that changed to use the proper Java `javac`
>> compiler instead of Groovy, and some references to fixing build errors
>> with
>> java 8 as well.
>>
>> Can (Should?) we be using JVM and JDK 7 features in the code now? What
>> about lambdas and other JVM 8 features? I had an ideafrom somewhere that
>> we are restricted to Java 6, perhaps for some reason to do with jclouds?
>> But, that doesn't seem right...
>>
>> FYI, based on Oracle documentation [1] Java 6 'End of Public Updates' was
>> February 201, and for 7 it is April 2015. Their 'Premier Support' for Java
>> 6 will end on December 2015, and July 2019 for 7. We're good until March
>> of
>> 2022 for 8, with 'Extended Support' for that lasting until 2025!
>>
>> [1] http://www.oracle.com/technetwork/java/eol-135779.html
>>
>> Cheers,
>> Andrew.
>> --
>> -- andrew kennedy ? distributed systems hacker :
>> http://blog.abstractvisitorpattern.co.uk/ ;
>>
>>
>
Re: Java Seven and Eight
Posted by Aled Sage <al...@cloudsoftcorp.com>.
Hi Andrew,
To-date, Brooklyn supports Java 1.6 and 1.7. It probably (?) supports
1.8 - I'm not sure if enough QA has been done on that yet.
Could folk who are using Java 8 shout out to let us know how that's
working out?
---
For dropping 1.6 support, jclouds talked about doing that when they
release 2.0.0 I think. I don't think there's a timeframe for that yet.
When jclouds drop support, then we'll definitely do so (if we haven't
already).
We've talked to a few enterprise users who have all been fine with
dropping 1.6 support, but we haven't talked to enough of them or looked
for feedback on the mailing list yet. If there is a big benefit, then we
could discuss doing that - for after 0.7.0 is released so we can warn
people that 0.7.0 will be the last release supporting java 1.6?
We should keep supporting 1.7 for the foreseeable future (at least until
the majority of enterprises have switched to Java 8). So no JVM 8
features in Brooklyn unfortunately.
Aled
On 10/02/2015 21:14, Andrew Kennedy wrote:
> Hi.
>
> What is our current policy for Java 1.7.x and 1.8.x usage? I see that there
> have been some recent PRs that changed to use the proper Java `javac`
> compiler instead of Groovy, and some references to fixing build errors with
> java 8 as well.
>
> Can (Should?) we be using JVM and JDK 7 features in the code now? What
> about lambdas and other JVM 8 features? I had an ideafrom somewhere that
> we are restricted to Java 6, perhaps for some reason to do with jclouds?
> But, that doesn't seem right...
>
> FYI, based on Oracle documentation [1] Java 6 'End of Public Updates' was
> February 201, and for 7 it is April 2015. Their 'Premier Support' for Java
> 6 will end on December 2015, and July 2019 for 7. We're good until March of
> 2022 for 8, with 'Extended Support' for that lasting until 2025!
>
> [1] http://www.oracle.com/technetwork/java/eol-135779.html
>
> Cheers,
> Andrew.
> --
> -- andrew kennedy ? distributed systems hacker :
> http://blog.abstractvisitorpattern.co.uk/ ;
>