[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Scout contribution disabled after m2e update
|
Just wanted to note that m2e usage questions are better taken place at:
https://github.com/eclipse-m2e/m2e-core/discussions
instead of the (cross-project) mailing list, this makes it easier to
focus on the particular problem and even link to the code.
Am 08.08.22 um 15:15 schrieb Arthur van Dorp:
Thanks Aleksander! My fault was looking at latest and snapshot. I should
have navigated to
https://download.eclipse.org/technology/m2e/releases/2.0.1/
<https://download.eclipse.org/technology/m2e/releases/2.0.1/>
Regards,
Arthur
--
<https://services.bsi-software.com/studio/public/e/l/bsi-signatur-logo>
BSI Business Systems Integration AG
Täfernweg 1, CH-5405 Baden
Telefon +41 58 255 93 23
www.bsi-software.com
<https://services.bsi-software.com/studio/public/e/l/bsi-signatur-url>_
_<https://services.bsi-software.com/studio/public/e/l/bsi-signatur-linkedin><https://services.bsi-software.com/studio/public/e/l/bsi-signatur-xing><https://services.bsi-software.com/studio/public/e/l/bsi-signatur-twitter><https://services.bsi-software.com/studio/public/e/l/bsi-signatur-youtube><https://services.bsi-software.com/studio/public/e/l/bsi-signatur-facebook><https://services.bsi-software.com/studio/public/e/l/bsi-signatur-instagram><https://services.bsi-software.com/studio/public/e/l/bsi-signatur-kununu>
*From:* cross-project-issues-dev
<cross-project-issues-dev-bounces@xxxxxxxxxxx> *On Behalf Of *Aleksandar
Kurtakov
*Sent:* Monday, 8 August, 2022 14:24
*To:* Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
*Subject:* Re: [cross-project-issues-dev] Scout contribution disabled
after m2e update
On Mon, Aug 8, 2022 at 2:50 PM Arthur van Dorp
<Arthur.vanDorp@xxxxxxxxxxxxxxxx
<mailto:Arthur.vanDorp@xxxxxxxxxxxxxxxx>> wrote:
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
<https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2feclipse%2dscout%2fscout.sdk%2fblob%2freleases%2f12.0%2forg.eclipse.scout.sdk.s2e.ui%2fpom.xml&umid=e8c06c01-be32-4347-8661-7e5b0979a99a&auth=2553b7ee1b402f6c614d840b79175d8e10d66fea-94ca448945c49d8e06a796ee134036dd2055dc1c>
But in
https://github.com/eclipse-scout/scout.sdk/blob/releases/12.0/org.eclipse.scout.sdk/pom.xml
<https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2feclipse%2dscout%2fscout.sdk%2fblob%2freleases%2f12.0%2forg.eclipse.scout.sdk%2fpom.xml&umid=e8c06c01-be32-4347-8661-7e5b0979a99a&auth=2553b7ee1b402f6c614d840b79175d8e10d66fea-04449d4d8cc31be69fc9ece29aaa22e861b719c5>
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/
<https://download.eclipse.org/technology/m2e/releases/latest/plugins/>
and the snapshots at
https://download.eclipse.org/technology/m2e/snapshots/latest/plugins/ <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?
Much like in the past - each bundle is versioned separately. Due to no
change in m2e.core it has no version change so it stays 2.0.0 and it's
safe to use it that way.
Thanks and kind regards,
Arthur
*From:* cross-project-issues-dev
<cross-project-issues-dev-bounces@xxxxxxxxxxx
<mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx>> *On Behalf Of
*Mickael Istria
*Sent:* Friday, 5 August, 2022 22:56
*To:* Cross project issues <cross-project-issues-dev@xxxxxxxxxxx
<mailto:cross-project-issues-dev@xxxxxxxxxxx>>
*Subject:* [cross-project-issues-dev] Scout contribution disabled
after m2e update
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 <https://www.eclipse.org/eclipseide> developer, for Red
Hat Developers <https://developers.redhat.com/>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
<mailto:cross-project-issues-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
<https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev>
--
Aleksandar Kurtakov
Red Hat Eclipse Team
_______________________________________________
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