[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] M2Eclipse @ Eclipse and/or Sonatype
|
m2e core 1.0.0 uses different namespace (org.eclipse.m2e vs
org.maven.ide.eclipse) and is NOT backwards compatible with 0.12 and
earlier versions. Old extensions will not work and there is no
0.12->1.0.0 workspace migration.
Eclipse has rather strict policies regarding API compatibilities for
"mature" projects, i.e. version >= 1.0.0, so our goal is to make sure
extensions developed for 1.0.0 will continue to work with future m2e
core versions.
To help users find and install extensions, we setup m2e
extensions catalog and introduced ability to automatically discover and
install required m2e extensions. In many cases m2e 1.0.0 will offer
installation of required software as part of project import wizard or
from a quick-fix for some error markers. It is also possible to access
m2e discovery catalog manually from Preferences->Maven->Discovery.
We have not decided what to do with Sonatype update sites yet.
--
Regards,
Igor
On 11-06-22 8:27 AM, Michael Pellaton wrote:
Hello
Until Helios we were using M2Eclipse plus some additional features from
the ext update site and we obtained all the files from Sonatype's two
update sites (core and ext).
Now, with the core part being released at Eclipse, what is the relation
between the core in the Indigo update site and the additional features
in Sonatype's ext update site?
Up to now, M2Eclipse was very particular about compatibility of the
different features. How is that now? Can the features 0.12 currently on
the ext update site be used with the 1.0 core from Indigo?
The IUs we are used to install are:
- org.maven.ide.eclipse.feature.feature.group --> now at Eclipse.org
- org.maven.ide.eclipse.wtp.feature.feature.group --> ?
Thanks for clarifiaction
Michael
