> Are you sure you are asking question in the right mailing list? :)
Yes :)
> We couldn't possible know what bugs some random Maven version has.
I know but since you're using the embedded maven 2.1 you should be
warned about this jaxws problem.
> 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.
It's a bug in Maven 2.1 and still not fixed.
> That doesn't mean that m2eclipse team can fix all bugs found in Maven 2.1.
Nope, I was asking if there is a way for m2eclipse to use an external
maven 2.0 for its internal operations
> 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.
Allreadu ask but ... who care ;(
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
