Wayne, I think you could be right. It's also possible though that the pom isn't intended to be run using 'mvn dependency:unpack' (I haven't looked at their site) because the pom is setup correctly to unpack during the package phase. I know this issue is a tricky one because the first time someone reported it, it took me quite a while to track it down. That's why I wrote the faq entry but maybe it's not clear enough. I'll have to look at it some more to see if I can present a more clear answer.
--Brian -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 20, 2007 9:13 PM To: Maven Users List Subject: Re: mvn dependency:unpack I think the primary problem is that muhwas is, in all likelihood, very new to Maven and so all the information you provide on the FAQ will probably be mostly insufficient to help him fix this issue. He simply lacks the base level of Maven knowledge to make the correct decisions about what goes in artifactItems and what does not. So, I think bouncing this "support" request over to the appropriate party is probably more reasonable. Someone in the Tuscany project (who created this pom in the first place) is probably the one who should fix the problem. Wayne On 3/20/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > The problem is exactly as the faq describes. Perhaps I need to clarify > some more in the faq... When you invoke a plugin from the cli that has > configuration in the pom, that configuration must _not_ be contained > inside an executions tag. I really think we need to look at changing > that because it causes lots of user confusion (this is a maven thing, > not a dependency plugin thing). Take a look at the second example on the > usage page: > > If you intend to configure this mojo for execution on the command line > using: > > mvn dependency:copy > > you must not put the configuration inside the executions tag. Your > configuration should look like this: > > <project> > [...] > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-dependency-plugin</artifactId> > <configuration> > <artifactItems> > <artifactItem> > <groupId>[ groupId ]</groupId> > <artifactId>[ artifactId ]</artifactId> > <version>[ version ]</version> > <type>[ packaging ]</type> > <overWrite>[ true or false ]</overWrite> > <outputDirectory>[ output directory ]</outputDirectory> > <destFileName>[ filename ]</destFileName> > </artifactItem> > </artifactItems> > <!-- other configurations here --> > </configuration> > </plugin> > </plugins> > </build> > [...] > </project> > > -----Original Message----- > From: muhwas [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 20, 2007 5:18 PM > To: Maven Users List; Brian E. Fox > Subject: RE: mvn dependency:unpack > > thank you for your reply but i am still getting same eror. could you > please let me know what i am doing wrong. > > thanks > > > --- "Brian E. Fox" <[EMAIL PROTECTED]> wrote: > > > I recently enhanced the plugin page to cover this > > specifically: > > > http://maven.apache.org/plugins/maven-dependency-plugin/faq.html > > > > -----Original Message----- > > From: muhwas [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 20, 2007 4:09 PM > > To: users@maven.apache.org > > Subject: mvn dependency:unpack > > > > hi, > > > > Can somebody please explain me how "mvn dependency:unpack" works > > because i am trying to run > > tuscany-incubating-M2 samples. when i run "mvn dependency:unpack" i am > > > getting > > > > [INFO] > > > ------------------------------------------------------------------------ > > [INFO] One or more required plugin parameters are invalid/missing for > > 'dependen y:unpack' > > > > [0] inside the definition for plugin: > > 'maven-dependency-plugin'specify the foll > > wing: > > > > <configuration> > > ... > > <artifactItems>VALUE</artifactItems> > > </configuration>. > > > > > > I found on the list that i have to include > > > > <plugin> > > > > <groupId>org.apache.maven.plugins</groupId> > > > > <artifactId>maven-dependency-plugin</artifactId> > > <version>2.0-alpha-1</version> > > <executions> > > <execution> > > <id>unpack</id> > > <phase>package</phase> > > <goals> > > <goal>unpack</goal> > > </goals> > > <configuration> > > <artifactItems> > > <artifactItem> > > <groupId>myModule</groupId> > > <artifactId>myArtifactId</artifactId> > > <version>1.0-SNAPSHOT</version> > > <type>jar</type> > > <overWrite>false</overWrite> > > > > > <outputDirectory>${project.build.directory}</outputDirectory> > > </artifactItem> > > </artifactItems> > > </configuration> > > </execution> > > </executions> > > </plugin> > > > > in the <plugins> section in pom.xml file. but i what to know how do i > > know what plug-ins to unpack? > > > > regards, > > muhwas > > > > > --------------------------------------------------------------------- > > 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]
