Hi Mickael, Can we respin 2021-06 RC1 to include m2e 1.18.0? If so, that would be my vote. Based on your message about laptop this seems unlikely?
It seems problematic to change m2e for RC2 as that will leave almost 0 testing time on the new integration. Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Thu, 3 Jun 2021 at 12:54, Mickael Istria <mist...@redhat.com> wrote: > Hi all, > > As mentioned in another thread, m2e has an important bug with Platform > 4.20 and SLF4J 2.0, causing build output to not appear in the console. This > issue is fixed in m2e and we can try releasing m2e 1.18.0 for SimRel > 2021-06. > However there are a lot of other changes in m2e 1.18.0 compared to m2e > 1.17.2 which is currently in SimRel ( > https://github.com/eclipse-m2e/m2e-core/compare/1.17.2...master ); so > this is not necessarily a trivial change and can be risky. But m2e has an > extensive test suite which IMO makes it relatively safe to adopt m2e. > So 2 solutions: > * Either we keep m2e 1.17.2 in 2021-06 with the bug and just tell people > who face it to update to m2e 1.18.0, or > * we rush a m2e 1.18.0 in 2021-06, which can be a source of quirks in the > release process (especially since my work laptop just died so I'm not going > to be very efficient at it) > > Cheers, > > -- > Mickael Istria > Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> > developer, for Red Hat Developers <https://developers.redhat.com/> > _______________________________________________ > 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 >
_______________________________________________ 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
