Write an issue and attach your pom (or reopen mdep-27 and attach) but I just looked at the exact same issue and it was working ok. This is the one I referenced in my post below http://www.nabble.com/dependency-plugin-at-maven.org-tf3019806.html. There must be something to this because multiple people have seen it, but I haven't been able to reproduce it yet.
--Brian -----Original Message----- From: Riboe, Jens [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 06, 2007 8:00 AM To: Maven Users List Subject: RE: 'dependency:copy' does not work >> However it appears that some people want to use >> it from the CLI (which the goal wasn't originally conceived to do) I didn't. It was bound to the package phase and I run 'mvn package' >> -----Original Message----- >> From: Brian E. Fox [mailto:[EMAIL PROTECTED] >> Sent: den 6 februari 2007 12:03 >> To: Maven Users List >> Subject: RE: 'dependency:copy' does not work >> >> I checked the documentation again last night. The descriptions for >> dependency:copy assume that it will be bound to a lifecycle. Therfore, >> the example is correct. However it appears that some people want to use >> it from the CLI (which the goal wasn't originally conceived to do), >> therefore the docs need to be augmented. I really think though that the >> root of the issue is a maven core issue. I don't understand why when >> executed from the CLI, it uses configuration from a tag outside an >> execution. It is obviously confusing. >> >> -----Original Message----- >> From: Riboe, Jens [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, February 06, 2007 2:33 AM >> To: Maven Users List >> Subject: RE: 'dependency:copy' does not work >> >> >> >> I think you are having this problem I described here: >> From that entry I got "I was able to configure the old one". >> >> I am not really sure I understand the point of publishing a plug-in >> description to the Maven site, which does not work when taken directly >> from it by cut-and-paste. >> >> The maven-changelog-plugin is sort of similar in that it is not >> available from ibiblio. You get the message 'does not exist or no valid >> version could be found' when trying to use it. >> >> Is it not sort of a minimum standard that one at least can trust the >> information published on the official web page? >> >> /Jens >> >> >> -----Original Message----- >> >> From: Brian E. Fox [mailto:[EMAIL PROTECTED] >> >> Sent: den 5 februari 2007 23:38 >> >> To: Maven Users List >> >> Subject: RE: 'dependency:copy' does not work >> >> >> >> I think you are having this problem I described here: >> >> >> http://www.nabble.com/dependency-plugin-at-maven.org-tf3019806.html#a840 >> >> 6709 >> >> >> >> (assuming you are copying dependency:copy from the command line?) >> >> >> >> -----Original Message----- >> >> From: Riboe, Jens [mailto:[EMAIL PROTECTED] >> >> Sent: Monday, February 05, 2007 6:22 PM >> >> To: Maven Users List >> >> Subject: RE: 'dependency:copy' does not work >> >> >> >> >> Do you have <artifactItems> element defined in your configuration? >> >> Yes. Exactly as stated in the docs >> >> <plugin> >> >> <groupId>org.apache.maven.plugins</groupId> >> >> <artifactId>maven-dependency-plugin</artifactId> >> >> <executions> >> >> <execution> >> >> <id>copy</id> >> >> <phase>package</phase> >> >> <goals> >> >> <goal>copy</goal> >> >> </goals> >> >> <configuration> >> >> <artifactItems> >> >> <artifactItem> >> >> <groupId>junit</groupId> >> >> <artifactId>junit</artifactId> >> >> <version>3.8.1</version> >> >> <type>jar</type> >> >> <overWrite>false</overWrite> >> >> >> >> >> <outputDirectory>${project.build.directory}/alternateLocation</outputDir >> >> ectory> >> >> <destFileName>optional-new-name.jar</destFileName> >> >> </artifactItem> >> >> </artifactItems> >> >> >> >> <outputDirectory>${project.build.directory}/wars</outputDirectory> >> >> <overWriteReleases>false</overWriteReleases> >> >> <overWriteSnapshots>true</overWriteSnapshots> >> >> </configuration> >> >> </execution> >> >> </executions> >> >> </plugin> >> >> >> >> >> >> >> >> >> -----Original Message----- >> >> >> From: Dan Tran [mailto:[EMAIL PROTECTED] >> >> >> Sent: den 5 februari 2007 22:52 >> >> >> To: Maven Users List >> >> >> Subject: Re: 'dependency:copy' does not work >> >> >> >> >> >> Do you have <artifactItems> element defined in your configuration? >> >> >> >> >> >> On 2/5/07, Riboe, Jens <[EMAIL PROTECTED]> wrote: >> >> >> > >> >> >> > I did a cut-and-paste from the docs of the dependency plug-in >> >> >> > >> >> >> > >> >> >> http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying >> >> >> > -artifacts.html >> >> >> > To troubleshoot my configuration of 'dependency:copy' >> >> >> > >> >> >> > However, I still get the same error as shown below. What am I >> doing >> >> >> > wrong and how is that reflected in the online docs? >> >> >> > >> >> >> > [INFO] >> >> >> > >> >> >> ------------------------------------------------------------------------ >> >> >> > [ERROR] BUILD ERROR >> >> >> > [INFO] >> >> >> > >> >> >> ------------------------------------------------------------------------ >> >> >> > [INFO] One or more required plugin parameters are >> invalid/missing >> >> for >> >> >> > 'dependency:copy' >> >> >> > >> >> >> > [0] inside the definition for plugin: >> >> 'maven-dependency-plugin'specify >> >> >> > the following: >> >> >> > >> >> >> > <configuration> >> >> >> > ... >> >> >> > <artifactItems>VALUE</artifactItems> >> >> >> > </configuration>. >> >> >> > >> >> >> > [INFO] >> >> >> > >> >> >> ------------------------------------------------------------------------ >> >> >> > [INFO] For more information, run Maven with the -e switch >> >> >> > [INFO] >> >> >> > >> >> >> ------------------------------------------------------------------------ >> >> >> > [INFO] Total time: 4 seconds >> >> >> > [INFO] Finished at: Mon Feb 05 22:18:41 GMT 2007 >> >> >> > [INFO] Final Memory: 8M/15M >> >> >> > [INFO] >> >> >> > >> >> >> ------------------------------------------------------------------------ >> >> >> > >> >> >> > >> >> >> > >> >> --------------------------------------------------------------------- >> >> >> > 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] >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> 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] >> >> >> >> >> --------------------------------------------------------------------- >> 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]