Frédéric,
Thank you for pointing us to the s/o post and the corresponding bug, saved us some time.
1) Yes, you won’t be able to install the m2e update into MyEclipse as there are hard constraints internally which will cause conflicts, as you have already seen.
2) Here’s a workaround that should work for you, until we fix this in the next MyEclipse release. We tested this internally and it fixed the issue for us:
a) Download attached zip file.
b) Shut down MyEclipse.
c) In your MyEclipse installation’s plugins
directory, you will find a file named: org.sonatype.m2e.mavenarchiver_0.17.2.201606141937-signed-20160830073346.jar
– make a backup of this file.
c) Unzip the zip into the plugins
directory, it will overwrite the above file.
d) Start MyEclipse.
So that you understand what is happening, we’ve just taken the 1.7.4 plugin and renamed it to have the same name as the 1.7.2 version already used in MyEclipse. Please let us know if this fixes the issue for you. We’ll ensure that this fix is part of the next MyEclipse update.
Attachments:
You must be
logged in to view attached files.