Re: [cross-project-issues-dev] FW: Re: [eclipse-ide-wg] [eclipse-pmc] Fwd: IMHO serious issues in the Eclipse Java IDE 2021-06 M3

Thu, 03 Jun 2021 05:30:19 -0700

The issue is now the Import-Package for the jetty bundles have a non-optional import on the slf4j package with a range forcing it to be 2.0:
 
For example:
https://search.maven.org/artifact/org.eclipse.jetty/jetty-io/10.0.2/jar
 
 
Has this import:
 
org.slf4j;version="[2.0.0,3)"
 
If this either had a range that included 1.x, or was made an optional import then it would allow us to keep using the current stable version of slf4j (the latest 1.x version).  As far as I can tell slf4j 2.0 is has not released a final version.  It seems to have been in a perpetual alpha state since 2019.

Tom
 
 
 
----- Original message -----
From: Jesse McConnell <[email protected]>
Sent by: "cross-project-issues-dev" <[email protected]>
To: Cross project issues <[email protected]>
Cc:
Subject: [EXTERNAL] Re: [cross-project-issues-dev] FW: Re: [eclipse-ide-wg] [eclipse-pmc] Fwd: IMHO serious issues in the Eclipse Java IDE 2021-06 M3
Date: Thu, Jun 3, 2021 5:30 AM
 
From the jetty perspective, you don't need to use a slf4j version 2 unless you're making use of the JPMS features. I believe you should be fine just running with the older version of slf4j.
 
On Wed, Jun 2, 2021, 05:58 Sravan K Lakkimsetti <[email protected]> wrote:

Slf4j version 2 dependency is coming from jetty 10. At platform we are consuming jetty. This is where the slf4j.api version 2 is coming from. Since Jetty stopped building p2 repositories we built jetty p2 repositories with bare minimum components that are required for platform.

 

We tried to use update Jetty around 2021-03 M3. But we thought this upgrade will be disruptive so we postponed to 2021-06 M1.

 

We added the feature announcement in N&N https://www.eclipse.org/eclipse/news/4.20/platform_isv.php#jetty-10-update

We also sent a note because of jetty upgrade there are conflicts in simrel to crossproject-dev list. There was a considerable discussion on this topic.

 

I am just listing what happened with update Jetty 10. Now we cannot go back to older version of slf4j that means downgrading Jetty. Now what should be the way forward?

 

-Sravan

 

From: Mickael Istria <[email protected]>
Sent: 02 June 2021 14:49
To: [email protected]
Cc: Discussions on Eclipse IDE Working Group <[email protected]>
Subject: [EXTERNAL] Re: [eclipse-ide-wg] [eclipse-pmc] Fwd: [cross-project-issues-dev] IMHO serious issues in the Eclipse Java IDE 2021-06 M3

 

Thanks for raising this issue folks. About Orbit or not, I fail at seeing what would that change: if slf4j 2.0 -which is a requirement- were in Orbit, how would that have prevented this issue in m2e from happening? ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍

Thanks for raising this issue folks.

About Orbit or not, I fail at seeing what would that change: if slf4j 2.0 -which is a requirement- were in Orbit, how would that have prevented this issue in m2e from happening?

_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
 


_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to