On 4/2/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
Try the fully qualified plugin name ie: -Dplugin=org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
This works, and pulls down the correct version from central. However, now that the new version is available, it is still resolving to org.codehaus.mojo:dependency-maven-plugin:1.0 I am running mvn dependency:analyze How do I run the same command but fully qualifying the plugin? Next question would be to work out why Maven is resolving codehaus first. If I recall correctly the expansion of <plugin>:<goal> first checks codehaus with <plugin>-maven-plugin and then checks central with maven-<plugin>-plugin. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
