On 4/13/07, ArneD <[EMAIL PROTECTED]> wrote:
To adress these issues, may I suggest the following: - Build Maven distributions that include a super POM that declares the latest stable(!) version of all core Maven plugins (i.e. the plugins hosted on maven.apache.org).
That won't work. You couldn't expect a corporate pom to be changed that often.
- Provide a downloadable distribution that is completely independent of repo1, i.e. a distribution that contains all Maven core plugins (in form of a pre-filled local repository, for example) in the latest stable version
Not sure I follow but I don't see how it will fix the problem. Stéphane
Regards - Arne -- View this message in context: http://www.nabble.com/Remove-auto-resolution-of-plugin-versions-from-Maven-2.1-tf3560617s177.html#a9975501 Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
