Henri Gomez wrote:
I am not exactly sure where you get apache-maven-2.1-659801
Q4E has some snapshots :)
Are you sure you are asking question in the right mailing list? :)
We couldn't possible know what bugs some random Maven version has.
but if you are able to reproduce this issue from the command line with this
Maven version, it would make sense to open JIRA issue on MNG project and/or ask
about it in Maven's user list.
Bugs allready opened, http://jira.codehaus.org/browse/MNG-3586.
That doesn't quite answers my question. If it is a bug in Maven 2.1 it
is not going to work in m2eclipse and someone from Maven team would have
to look at this.
However if it does work from the command line with Maven 2.1 and only fail
in m2eclipse, then please cubmit bug report to m2eclipse and attach a simple
test project that would allow us to reproduce it.
m2eclipse use embedded maven for all of its internal operation ?
Selecting the maven (embedded or externals) only works when doing Run
Maven ... ?
That doesn't mean that m2eclipse team can fix all bugs found in Maven
2.1. We would love to help you, but unfortunately our time and resources
are not infinite. We did contributed some patches to Maven in a past to
fix most common issues, but for fundamental things like classloading,
backward incompatibility with Maven 2.0 for some plugins (like in your
case) and other core issues you really need to talk to the Maven team.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
