ace-dev mailing list archives

Hello Niclas,
I like making this a two step approach. I guess I would start using Java 8 and have its compiler
produce Java 7 compatible bytecode for now and then, a few releases later, start leveraging
Java 8.
Greetings, Marcel
On 2 Apr 2015 at 22:01:02, Niclas Hedhman (niclas@hedhman.org) wrote:
Oracle is really aggressive in pushing the "HEAD" of us "freeloaders" who
doesn't want to pay for the support. What they might not realize is that;
As ASF projects are forced to higher versions, the whole enterprise world
will have to follow suit very quickly and the revenue might not be as high
as Oracle expects (from looking at past upgrade speeds)...
Well, I like Java 8 so much, that I am all in favor of Java 8, but
typically I would recommend;
Step 1) Make it Java 8 compatible, and run the CI on both Java 7 and Java
8 for a while. Release artifacts in Java 7 format.
Step 2) Allow ACE to use Java 8 features internally, drop Java 7 support
totally, ship in Java 8 byte code format.
Not sure what is a reasonable time period in between, but my guess 2
releases or so would be adequate... ;-)
Niclas
On Thu, Apr 2, 2015 at 10:45 PM, Marcel Offermans <
marcel.offermans@luminis.nl> wrote:
> Hey all,
>
> As previously announced on Oracle’s roadmap, they will stop updating Java
> 7 [1] as of this month. As a consequence, I think we should discuss moving
> Apache ACE to Java 8. My first question is, does anybody object to that
> (then this is the time to speak up)?
>
> Greetings, Marcel
>
>
> [1]
> http://www.oracle.com/technetwork/java/eol-135779.html#Java6-end-public-updates
>
>
>
>
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java