|Re: [eclipse-pmc] [cross-project-issues-dev] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...|
letting things (like Help) fail seems not very nice from the user’s point of view. I would vote for requiring Java 11 at the start.
@Dani: Do you also have answers to my other questions?
It depends. We (the platform) can require/hardcode Java 11 when you start the SDK or we do not enforce this but let things like Help/Jetty fail. Our position is that users need
Java 11 for 2020-09.
do I understand this correctly that the 2020-09 release needs at least a Java 11 VM to run? Will it no longer run on a Java 8 VM?
Will platform raise the Bundle-Execution Environment?
If release 2020-09 will only run on Java11 and newer: How does platform's "Check for Updates" handle this? What happens if a user has an existing installation running on Java 8 (and this is the user's one and only Java VM)? Does P2 tell the user that the new bundles to be installed require Java 11 but that the current installation does not supply this?
<eclipse-pmc-bounces@xxxxxxxxxxx> on behalf of Mike Wilson <Mike_Wilson@xxxxxxxxxx>
Hello cross project people,
The Eclipse Project PMC has approved a change to the target environments for the 2020-09 Eclipse release of the Eclipse Project (that is, our 4.17 release) to be based on Java 11. This will allow us to include Jetty 10, when it is available as indicated here:
Given that this change has the potential to impact downstream projects, we are asking for feedback now: please let us know if you believe this will cause problems for your project.
Note that we are not asking teams to update the BREE for their components, and it is fine for components to support earlier versions of Java. This note is just identifying the version of Java that we will use to validate the September release, and thus will be the supported version for the Eclipse SDK.
the Eclipse Project PMC
Back to the top