What
is the rationale for wanting to keep BREE levels as low as
possible? Even Java 7 enters the “no further public updates”
phase in April of this year. JRE 7 users in the normal
update pipeline were upgraded to Java 8 in January. Are
there really users out there who _cannot_ run a newer
version of the JRE despite security and performance
implications of running an old version? I am guessing that
if Mars were to require Java 8, there would be some initial
grumbling over having to upgrade, then everyone moves on in
a better and more secure configuration.
http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html
Thanks,
-
Konstantin
Hi
But this is important.
When osgi.utils moved from Java 5 to Java 6 that made Eclipse
almost unuseable as a Java 5 platform; not really a problem.
Now jdt.core does nearly the same thing for Eclipse as a Java
6 platform. Are we ready to go that far? IMHO it certainly
should be discussed and announced.
Regards
Ed Willink
On 04/03/2015 14:42, Daniel Megert wrote:
Hi
Ed
Yes,
this was intended. We never announce BREE changes.
Dani
From:
Ed
Willink <ed@xxxxxxxxxxxxx>
To:
Cross
project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:
04.03.2015
15:27
Subject:
[cross-project-issues-dev]
jdt.core move to Java 7 BREE
Sent
by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Hi
Is the recent change in BREE for org.eclipse.jdt.core
from Java 6 to
Java 7 intended?
Was it announced?
Regards
Ed Willink
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
No
virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5751 / Virus Database: 4299/9224 - Release
Date: 03/04/15