|Re: [cross-project-issues-dev] Kepler SR3 for Java 8?|
Well, it directly affects Maven builds. You can't use Java 8 by itself to build the platform aggregator, for example. You need to set up a toolchains.xml file to hook up Java 7 as well. And that's probably the solution here too. If you have plug-ins with BREE's of Java 7 or earlier, and plug-ins you've upgraded to Java 8, you need both JREs registered in your environment. I'm not sure there's actually any way around it. But at least the flexibility we have gives us a workaround.
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Sven Efftinge [sven.efftinge@xxxxxxxxx]
Sent: Thursday, March 27, 2014 6:18 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Kepler SR3 for Java 8?
I agree, that this is unfortunate and should be fixed.
But doesn’t that only affect users, who have installed Java 8 plus the Eclipse-support *and*
are using an environment for Java 8 but have the compiler set to something below 8?
Is that something many people do? If so they will likely run into many other problems, as they
now program against Java 8 JDK which has a lot of cool new classes and members that won’t be available as soon as they
run the code on a Java7 VM or compile it against a Java 7 JDK.
So IMHO this is not a stopper for having a more prominent download for the Java 8 support.
On 27 Mar 2014, at 09:59, Mickael Istria <mistria@xxxxxxxxxx> wrote:
Back to the top