RE: org.codehaus.mojo:dependency-maven-plugin takes precedence over org.apache.maven.plugins:maven-dependency-plugin

2007-05-14 Thread Brian E. Fox
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

Re: org.codehaus.mojo:dependency-maven-plugin takes precedence over org.apache.maven.plugins:maven-dependency-plugin

2007-05-11 Thread Wayne Fay
You should fully specify the plugin... + in the pom, make sure you specify the artifactId and groupId + on the command line, use groupId:artifactId:version:mojo, ie mvn org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack Wayne On 5/11/07, Graham Leggett [EMAIL PROTECTED]