The metadata at codehaus was cleaned up back when the plugin was rereleased from apache. Somewhere in your system/proxies, there is an old piece of the metadata. If you clean out /org/codehaus/mojo/maven-metadata.*, you should be ok. I recognize this is not ideal. This behavior is fixed in 2.0.7 under MNG2926, but until 2.0.7 comes out, refreshing the metadata, or fully specifying the plugin is the only workaround.
-----Original Message----- From: Graham Leggett [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 11:41 AM To: users@maven.apache.org Subject: org.codehaus.mojo:dependency-maven-plugin takes precedence over org.apache.maven.plugins:maven-dependency-plugin Hi all, I have been trying to configure the execution of the org.apache.maven.plugins:maven-dependency-plugin when the "dependency:unpack" goal is executed. According to the stacktrace I get, maven is trying to invoke the org.codehaus.mojo:dependency-maven-plugin instead - which has a completely different config syntax. How does maven resolve the situation where two different plugins are claiming the same namespace? Regards, Graham -- --------------------------------------------------------------------- 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]
