eclipse-platform / .github

Common contribution content for eclipse-platform repositories
https://www.eclipse.org/eclipse/
5 stars 10 forks source link

Eclipse 2022-09 M3 and RC1: Cannot install Maven Tycho Configurator #60

Closed svcacct-swup-build closed 2 years ago

svcacct-swup-build commented 2 years ago

Hi guys! Sorry, but I didn´t know where to report the issue I am experiencing. So I put it here. It is regarding the upcoming Eclipse version (2022-09). I have tried to install the Tycho Configurator by selecting this in the preferences on the M1 and M2 release by doing this:

Preferences -> Maven -> Discovery -> Open Catalog -> Tycho Configurator -> Finish.

... and that has worked fine. But since the M3 release (thus, also on the RC1), I get this:

Problem occured: Operation details Cannot complete the install because of a conflicting dependency. Software being installed: Tycho Project Configurators 0.9.0.201811261502 (org.sonatype.tycho.m2e.feature.feature.group 0.9.0.201811261502) Software currently installed: M2E - Maven Integration for Eclipse 2.0.2.20220828-2046 (org.eclipse.m2e.feature.feature.group 2.0.2.20220828-2046) Only one of the following can be installed at once: M2E Maven Integration for Eclipse Core 1.18.4.20220208-0831 (org.eclipse.m2e.core 1.18.4.20220208-0831) M2E Maven Integration for Eclipse Core 2.0.1.20220820-1147 (org.eclipse.m2e.core 2.0.1.20220820-1147) Cannot satisfy dependency: From: M2E - Maven Integration for Eclipse 2.0.2.20220828-2046 (org.eclipse.m2e.feature.feature.group 2.0.2.20220828-2046) To: org.eclipse.equinox.p2.iu; org.eclipse.m2e.core [2.0.1.20220820-1147,2.0.1.20220820-1147] Cannot satisfy dependency: From: Tycho Project Configurators 0.9.0.201811261502 (org.sonatype.tycho.m2e 0.9.0.201811261502) To: osgi.bundle; org.eclipse.m2e.core [1.4.0,2.0.0) Cannot satisfy dependency: From: Tycho Project Configurators 0.9.0.201811261502 (org.sonatype.tycho.m2e.feature.feature.group 0.9.0.201811261502) To: org.eclipse.equinox.p2.iu; org.sonatype.tycho.m2e [0.9.0.201811261502,0.9.0.201811261502]

selundqma commented 2 years ago

Ah.. It was me who reported it. I forgot to change from our generic GitHub account (svcacct-swup-build).

mickaelistria commented 2 years ago

Issue should be reported to https://github.com/tesla/m2eclipse-tycho , so far this connector is not managed by Tycho. However, it's not very clear what the future of this connector should be in order to make it more sustainable... Include it in m2e, include it in Tycho...?

laeubi commented 2 years ago

There is already:

selundqma commented 2 years ago

As long as it works in the release version of 2022-09 :). I wonder what broke it from the M2 to the M3 version.

laeubi commented 2 years ago

The Tycho connector is not supported anymore. As the 2022-09 release contains m2e 2.0 there will be no "fix" so if there is something you miss without using it you should report it here:

HannesWell commented 2 years ago

As long as it works in the release version of 2022-09 :). I wonder what broke it from the M2 to the M3 version.

It depends a bit on what you need from the connector. As the others said, because Eclipse 2022-09 will contain a new major version of M2E (i.e. M2E 2.0) and the Tycho connector only works with M2E 1.x, the connector itself does not work (yet) with M2E 2.0. Please note that since Tycho 2.7.4 lifecycle-mapping-metadata for all plug-ins are embedded into Tycho itself that state that those plug-in executions should be ignored, which silences the M2E warnings: https://github.com/eclipse-tycho/tycho/blob/master/RELEASE_NOTES.md#eclipse-m2e-lifecycle-mapping-metadata-embedded-1

If there is still something missing please report that to the M2E issue mentioned above.

kwin commented 1 year ago

It seems some fixes for m2e 2.x were applied upstream at https://github.com/tesla/m2eclipse-tycho/commit/9917ef1396334c81b99043049065bc40b1ad37dd.

laeubi commented 1 year ago

Pleas note that still Tycho connector is not supported by M2Eclipse or Tycho directly (even though indicated by the name), and I strongly recommend to not install it and instead contribute any missing functionality to m2e directly.