[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] FW: Re: [eclipse-ide-wg] [eclipse-pmc] Fwd: IMHO serious issues in the Eclipse Java IDE 2021-06 M3
|
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.
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
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
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev