| Re: [cross-project-issues-dev] Scout contribution disabled after m2e update |
|
Hi Mickael, Thanks for the heads up. I have never updated the m2e dependency myself before and I am a bit lost. For the Scout SDK UI plugin I plan to update the range to org.eclipse.m2e.core.ui;bundle-version="[2.0,2.1)" in
https://github.com/eclipse-scout/scout.sdk/blob/releases/12.0/org.eclipse.scout.sdk.s2e.ui/pom.xml But in
https://github.com/eclipse-scout/scout.sdk/blob/releases/12.0/org.eclipse.scout.sdk/pom.xml we reference very specific versions: <org.eclipse.m2e.core>1.18.4.20220208-0831</org.eclipse.m2e.core> <org.eclipse.m2e.core.ui>1.19.0.20220206-1032</org.eclipse.m2e.core.ui> <org.eclipse.m2e.archetype.common>1.18.1.20211011-2139</org.eclipse.m2e.archetype.common> The person usually updating those is currently unavailable, so I don’t know why that is. But looking at the m2e downloads I find the releases at https://download.eclipse.org/technology/m2e/releases/latest/plugins/ and the snapshots at https://download.eclipse.org/technology/m2e/snapshots/latest/plugins/ Both don’t have a m2e 2.0.1 core version (only 2.0.0). Am I looking at the wrong place? Thanks and kind regards, Arthur From: cross-project-issues-dev <cross-project-issues-dev-bounces@xxxxxxxxxxx>
On Behalf Of Mickael Istria Hi all, I updated SimRel to use new m2e 2.0.1 release. This is a new major version compared to previously contributed 1.20.1, so some dependency ranges need to be updated in customers, and probably some code as well. Scout is currently not compatible, because of a requirement on an older version of m2e. I had to disable it for the moment. I recommend Scout maintainers to evaluate migration to m2e 2.0.1 ASAP to ensure both can participate simultaneously in SimRel. Cheers, Mickael Istria Eclipse IDE developer, for
Red Hat Developers |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature