Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [eclipse-pmc] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...
  • From: "Becker, Matthias" <ma.becker@xxxxxxx>
  • Date: Wed, 25 Mar 2020 07:50:23 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sap.com; dmarc=pass action=none header.from=sap.com; dkim=pass header.d=sap.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ATxJgofiKyNHRkh4rTjZv7Bu1S7g3yS6wQPlLyKQNm4=; b=V266Ux36H6vDZzcvYCd54nbn0VjPljoSSuJ/1vljRKxYndwsq6YB2VQG+kdbQOFUMpFLcyEptyXgc5+V7nolliCfAYzxq9m9Lyo/BAnaqGvLt04zImBZ+beI6ovFcIYA08/zHBVzujlems5v/7rr/VCZmJ9aS/Vwu3NdpGPVlIqlIAgv52FFba1vnb5bWl/xTqEyS+kqJsnhjOc+zkSl/UsBz0XcIbKQTusmCeJ3ciOgP2yqEltUscrVt9p5Wn9Nud9Ch6R6FfVxR1usT7KXbIa+e08PmdVOOTmdJhB0LvqlH9vTKY0I369szv6j++C9yMwHY2SBdUwSrqFQKJEDBA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Mfbvqdv7vaoQwoAVH3q1G53MVdqhTvOKjrm6XXVqKTyDx6e9U1XFptZ8UcAcQMHIjCwDqtQ0TzQLnIt1dWfG92qa34m/3L+csrTDOKmyBt9VOTrGLlXQGlBEOQQmRBaudbGwliPWKeFydLFGXO7EWaoNhmpiYdofFoWwqvKE6HMFS4aZDt5p9hMOuzTEkIZAzUy+xbyCZC1XJJqbzxekj17zHttVgCy3+hwQ+ki7CtNZe/WseSSwRVaG/2LfN0EwTh5x+J4XPpZbGD2CVzC1QTS0qyHD7dR/vwre38D3tN7OVKi6EFPJPjEjK9BJjjdJjHsZIsAyUaIqv/BQIQAL9w==
  • Delivered-to: cross-project-issues-dev@xxxxxxxxxxx
  • Ironport-sdr: lNHBJUm16NP0B0LcTBM1K3tMOvbgFHOsMlSIMXLXFWRfqHjLIHTbhYuKaXF+rUvo6K1VTu9fAV NucMfzht+JCkrANNK/lbXEDxjgNo6LrV5kXtsh7JjGk6nRPhcFE6A0MzEpr6+cJPIdYDXiQHbP S15BVy/cLCYPcZvuHWVO67W29GGIbir9Ic+fnkRUII4WJSDd3u1oum4eJXnOWF4/4L1vmRQRuW 4AHqxipwsYZ8wXViRVbXxphqw0ls5qcmnVTFotdJd/m/e0RLy9w6zL7g3+2OeIaC5JRLww7//z a+1LiZNXXLfU0No0+hG5ItvB
  • List-archive: <https://www.eclipse.org/mailman/private/cross-project-issues-dev>
  • List-help: <mailto:cross-project-issues-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHWASeY5qPfU0D2sEGdwWt+vUigGahWbSoAgAElMICAAXArgA==
  • Thread-topic: [cross-project-issues-dev] [eclipse-pmc] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...
  • User-agent: Microsoft-MacOutlook/16.35.20030802

Hi Ed,

 

so what do you propose?


Regards,

Matthias

 

From: <cross-project-issues-dev-bounces@xxxxxxxxxxx> on behalf of Ed Merks <ed.merks@xxxxxxxxx>
Reply to: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: Tuesday, 24. March 2020 at 11:53
To: "cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] [eclipse-pmc] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...

 

It's not until the bundles are started that one knows their BREEs.  The launcher only knows the value for -Dosgi.requiredJavaVersion=1.8 from the eclipse.ini and that it already checks.  I believe there are issues with restart after update not actually reading the eclipse.ini.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=531112

In any case, if the product changes the Dosgi.requiredJavaVersion value during update, and product will not start (with a semi-help message) when started from scratch if the specified or implicit JVM is not at least that high.  This will no doubt create endless grief for users who use the updates to keep their IDE update-to-date and perhaps that is even more painful than help not working...  At least help not working could be explained to the user via something else that doesn't require Java 11 to explain the problem...

 

On 23.03.2020 18:23, Ed Willink wrote:

Hi

I thought I had raised a Bugzilla on this but cannot find it.

IMHO the eclipse.exe launcher should diagnose the suitability of the user's platform for Eclipse and provide helpful diagnostics rather than a Java bang dialog. This should all be done before Java is started. Wrong Java version is an obvious check. Historically, the Microsoft Java was a regular user hazard.

    Regards

        Ed Willink

On 23/03/2020 15:25, Daniel Megert wrote:

HI Matthias

> 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.
I agree.

I'm not a p2 expert, so,, no, I can't answer your question to an end, but I assume that it won't warn and just fail on restart.

Dani



From:        "Becker, Matthias" <ma.becker@xxxxxxx>
To:        "eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>, Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        23.03.2020 13:59
Subject:        [EXTERNAL] Re: [cross-project-issues-dev] [eclipse-pmc] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx


 

Hi Dani,

 

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?


Regards,

Matthias

 

From: <eclipse-pmc-bounces@xxxxxxxxxxx> on behalf of Daniel Megert <daniel_megert@xxxxxxxxxx>
Reply to:
"eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>
Date:
Monday, 23. March 2020 at 13:33
To:
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc:
"cross-project-issues-dev-bounces@xxxxxxxxxxx" <cross-project-issues-dev-bounces@xxxxxxxxxxx>, "eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>
Subject:
Re: [eclipse-pmc] [cross-project-issues-dev] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...

 

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.

Dani




From:        
"Becker, Matthias" <ma.becker@xxxxxxx>
To:        
"eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>, "cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx>
Date:        
23.03.2020 10:57
Subject:        
[EXTERNAL] Re: [cross-project-issues-dev] [eclipse-pmc] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...
Sent by:        
cross-project-issues-dev-bounces@xxxxxxxxxxx


 

Hi everybody,

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?

Regards,

Matthias

 

From: <eclipse-pmc-bounces@xxxxxxxxxxx> on behalf of Mike Wilson <Mike_Wilson@xxxxxxxxxx>
Reply to:
"eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>
Date:
Friday, 20. March 2020 at 19:35
To:
"cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx>
Cc:
"eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>
Subject:
[eclipse-pmc] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...

 

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:

    https://www.eclipse.org/lists/jetty-dev/msg03214.html

 

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.

 

thanks,

the Eclipse Project PMC


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev




_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

 

Image removed by sender.

Virus-free. www.avast.com



_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Back to the top