Henri Gomez wrote:
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
Unfortunately it is not possible, because Maven 2.0 is not embeddable.
By the way, I thought you are not using m2eclipse anymore...
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 ;(
There is always an alternative. For instance, you can also try to fix
it yourself, submit patches and eventually became Maven committer, so
everything would be fixed in a blink of your eye. ;-)
Seriously speaking, every team have priorities. There are over 600 bug
reports and enhancement requests issues open on Maven project. You can
do the math games to calculate how much time Maven team would need to
fix all of them. So, they have to prioritize what they believe is
important and take patches if someone contribute fixes to the low
priority issues.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
