Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-pmc] [eclipse-ide-wg] Fwd: [cross-project-issues-dev] IMHO serious issues in the Eclipse Java IDE 2021-06 M3

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 <mistria@xxxxxxxxxx>
Sent: 02 June 2021 14:49
To: eclipse-pmc@xxxxxxxxxxx
Cc: Discussions on Eclipse IDE Working Group <eclipse-ide-wg@xxxxxxxxxxx>
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?



Back to the top