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 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=574035> Bug 574035 - Update to Jetty 10.0.4. Can you please give a +1 on this effort. Thanks Sravan From: Mike Wilson <mike_wil...@ca.ibm.com> Sent: 05 June 2021 02:36 To: eclipse-...@eclipse.org Cc: eclipse-...@eclipse.org; eclipse.org-planning-coun...@eclipse.org 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. McQ. ----- Original message ----- From: "Thomas Watson" <tjwat...@us.ibm.com <mailto:tjwat...@us.ibm.com> > Sent by: "eclipse-pmc" <eclipse-pmc-boun...@eclipse.org <mailto:eclipse-pmc-boun...@eclipse.org> > To: eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> Cc: eclipse-...@eclipse.org <mailto:eclipse-...@eclipse.org> , eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> 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 <https://github.com/eclipse/jetty.project/issues/6354> ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd 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 <https://github.com/eclipse/jetty.project/issues/6354> Tom ----- Original message ----- From: "Thomas Watson" <tjwat...@us.ibm.com <mailto:tjwat...@us.ibm.com> > Sent by: "eclipse.org-planning-council" <eclipse.org-planning-council-boun...@eclipse.org <mailto:eclipse.org-planning-council-boun...@eclipse.org> > To: eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> , eclipse-...@eclipse.org <mailto:eclipse-...@eclipse.org> Cc: eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> 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 <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? Tom ----- Original message ----- From: Jonah Graham <jo...@kichwacoders.com <mailto:jo...@kichwacoders.com> > Sent by: "eclipse.org-planning-council" <eclipse.org-planning-council-boun...@eclipse.org <mailto:eclipse.org-planning-council-boun...@eclipse.org> > To: Eclipse Planning Council private list <eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> > 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, 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 showing correct versions as expected, so that is good. Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com <http://www.kichwacoders.com> On Fri, 4 Jun 2021 at 04:50, Ed Merks <ed.me...@gmail.com <mailto:ed.me...@gmail.com> > wrote: This is kind an ongoing nightmare because I already committed the catalog changes to refer to https://download.eclipse.org/justj/?file=releases/2021-06/202106041000 but now that needs to change to https://download.eclipse.org/justj/?file=releases/2021-06/202106041001 and I don't know if EPP needs to respin to produce yet something else new different from https://download.eclipse.org/technology/epp/packages/2021-06/202106031200/ to deal with these changes in SimRel... I tested with https://download.eclipse.org/justj/?file=releases/2021-06/202106041001 installed the Committers package with JustJ Java 16.0.1 and can see these installed: I'm not sure how to test that the m2e console is working properly... Let me hang out and await the latest surprises updates.... On 04.06.2021 09:57, Frederic Gurr wrote: Hi Jonah, Re-running the aggregator build updated only the staging repo. The missing step was promoting the staging repo to releases. I've fixed this with assistance from Mikael. RC1 had a lot of bad timing, including me not being near a laptop for a long weekend and having to do release engineering on a smartphone. :/ Regards, Fred On Thu, 3 Jun 2021, 20:57 Jonah Graham, <jo...@kichwacoders.com <mailto:jo...@kichwacoders.com> > wrote: Thank you Melanie. I have started the rebuild. @Frederic Gurr <mailto:frederic.g...@eclipse-foundation.org> - I hope I haven't done anything wrong - I have reenabled and triggered the build and will disable it when it is done again. Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com <http://www.kichwacoders.com> On Thu, 3 Jun 2021 at 14:37, Mélanie Bats <melanie.b...@obeo.fr <mailto:melanie.b...@obeo.fr> > wrote: Hi Jonah, Le 03/06/2021 à 19:39, Jonah Graham a écrit : > I submitted the simrel change for m2e - > https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/181395 > <https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/181395> > > I am concerned it is getting to be after work in Europe and less people > than normal would see this message. > > Can someone (planning council perhaps?) give me a +1 to rebuild RC1 so > that the EPP for RC1 tomorrow can have new m2e? +1 -- Mélanie Bats CTO +33 7 87 69 42 84 @melaniebats *Obeo* 25 Boulevard Victor Hugo - Colomiers - France http://www.obeo.fr <http://www.obeo.fr> _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-coun...@eclipse.org <mailto:eclipse.org-planning-coun...@eclipse.org> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council _______________________________________________ eclipse-pmc mailing list eclipse-...@eclipse.org <mailto:eclipse-...@eclipse.org> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
