[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-users] m2e and m2eclipse versions
|
I'm not sure Bugzilla offers the equivalent of JIRA's release notes and
I'm not aware of any official Release Notes statement for m2e, but for
the maven integration with WTP, you have :
v0.12.0 (works with m2e 0.12.x) :
* Release notes :
https://issues.sonatype.org/secure/ReleaseNote.jspa?projectId=10310&version=10937
* New and Noteworthy :
http://community.jboss.org/en/tools/blog/2011/05/03/m2eclipse-wtp-0120-new-noteworthy
v0.13.0 (works with m2e 1.0.x) :
* Release notes :
https://issues.sonatype.org/secure/ReleaseNote.jspa?projectId=10310&version=11013* New and Noteworthy :
http://community.jboss.org/en/tools/blog/2011/06/23/m2eclipse-wtp-0130-new-noteworthy
v0.13.1 (works with m2e 1.0.x) :
* Release notes :
https://issues.sonatype.org/secure/ReleaseNote.jspa?projectId=10310&version=11271
* New and Noteworthy :
http://community.jboss.org/en/tools/blog/2011/08/01/m2eclipse-wtp-0131-back-to-the-m2e-marketplace
And it's true there is no migration path between m2e 0.x and 1.x versions, so you'd better start from a fresh eclipse installation.
Regards,
Fred Bricon
2011/9/14 Guillaume Polet
<guillaume.polet@xxxxxxxxx>
Hi,
I don't have a changelog on this but I guess an m2e developer can easily fill you in on the major changes.
>From my point of view, m2eclipse works a lot better than it used to. Even better, m2e-wtp is a lot more usable than before.
However, one major drawback of upgrading was that I had to repair manually all my projects because it seems that the name of the classpath library "Maven container" changed its identifier (wondering why there was no automatic conversion of it). When I upgraded my workspace, I had to manually fix these Maven container issues. If you start on a fresh workspace, you won't see the difference.
Cheers,
Guillaume
Le 14/09/2011 11:39, Krämer, Michael a écrit :
--
"Have you tried turning it off and on again" - The IT Crowd