Hi, As I understand we will have fix this even if it means delaying eclipse release. If Platform is not able to get the build out before Wednesday June 9, Simrel will have to do a RC2 respin. For this effort I raised Bug 574035 - Update to Jetty 10.0.4. Can you please give a +1 on this effort. Thanks Sravan From: Mike Wilson <Mike_Wilson@xxxxxxxxxx> Sent: 05 June 2021 02:36 To: eclipse-pmc@xxxxxxxxxxx Cc: eclipse-pmc@xxxxxxxxxxx; eclipse.org-planning-council@xxxxxxxxxxx Subject: [EXTERNAL] Re: [eclipse-pmc] [eclipse.org-planning-council] [cross-project-issues-dev] m2e 1.18.0 and SimRel 2021-06 So, if it takes a week or even two, then that's what we should do. Release dates do not justify doing the wrong thing. ----- Original message ----- From: "Thomas Watson" <tjwatson@xxxxxxxxxx> Sent by: "eclipse-pmc" <eclipse-pmc-bounces@xxxxxxxxxxx> To: eclipse.org-planning-council@xxxxxxxxxxx Cc: eclipse-pmc@xxxxxxxxxxx, eclipse.org-planning-council@xxxxxxxxxxx Subject: [EXTERNAL] Re: [eclipse-pmc] [eclipse.org-planning-council] [cross-project-issues-dev] m2e 1.18.0 and SimRel 2021-06 Date: Fri, Jun 4, 2021 11:13 AM Update. I tried out the snapshot jetty bundles with the fix. It did allow me to remove slf4j 2.0. But it sounds like the earliest we would see a Jetty release with the fix is the middle/end of next week: https://github.com/eclipse/jetty.project/issues/6354 ZjQcmQRYFpfptBannerStart This Message Is From an External Sender | This message came from outside your organization. |
|
|
ZjQcmQRYFpfptBannerEnd ----- Original message ----- From: "Thomas Watson" <tjwatson@xxxxxxxxxx> Sent by: "eclipse.org-planning-council" <eclipse.org-planning-council-bounces@xxxxxxxxxxx> To: eclipse.org-planning-council@xxxxxxxxxxx, eclipse-pmc@xxxxxxxxxxx Cc: eclipse.org-planning-council@xxxxxxxxxxx Subject: [EXTERNAL] Re: [eclipse.org-planning-council] [cross-project-issues-dev] m2e 1.18.0 and SimRel 2021-06 Date: Fri, Jun 4, 2021 7:25 AM Not to throw a wrench into the whole plan here, but I did manage to get a PR merged into Jetty to allow 10.0.x Jetty to tolerate slf4j 1.7.x. I don't know the feasibility of either of these things but what if: 1) Jetty was able to quickly turn ZjQcmQRYFpfptBannerStart This Message Is From an External Sender | This message came from outside your organization. |
|
|
ZjQcmQRYFpfptBannerEnd Not to throw a wrench into the whole plan here, but I did manage to get a PR merged into Jetty to allow 10.0.x Jetty to tolerate slf4j 1.7.x. I don't know the feasibility of either of these things but what if:
1) Jetty was able to quickly turn around a service release of 10.0.x including the fix (https://github.com/eclipse/jetty.project/pull/6356) 2) The Eclipse project updated to the latest release and returned to pulling in the stable version of slf4j 3) Everything else on the train goes back to the way it was? Do we have time, is this possible? Wouldn't this be a better solution all around, even if it causes a delay? ----- Original message ----- From: Jonah Graham <jonah@xxxxxxxxxxxxxxxx> Sent by: "eclipse.org-planning-council" <eclipse.org-planning-council-bounces@xxxxxxxxxxx> To: Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx> Cc: Subject: [EXTERNAL] Re: [eclipse.org-planning-council] [cross-project-issues-dev] m2e 1.18.0 and SimRel 2021-06 Date: Fri, Jun 4, 2021 5:28 AM Hi Ed, The EPP builds from the staging repo, not from the release repo as the staging repo is what is in the announcement email - https://www.eclipse.org/lists/cross-project-issues-dev/msg18401.html. As for your screenshot, that seems to be ZjQcmQRYFpfptBannerStart This Message Is From an External Sender | This message came from outside your organization. |
|
|
ZjQcmQRYFpfptBannerEnd Hi Ed, As for your screenshot, that seems to be showing correct versions as expected, so that is good.
|