You have copy/unpack that lets you specify certain artifacts to manipulate that may not necessarilly be part of your dependencies (think zip files).
You also have copy-dependencies/unpack-dependencies that starts with the list of all dependencies and provides ways to filter that list down by transitivity/scope/group/artifactId/classifier etc. -----Original Message----- From: JavierL [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 25, 2007 4:00 PM To: [email protected] Subject: Re: jar with dependencies in a folder Wayne Fay wrote: > > Ah! In that case, you want to use the maven-dependency-plugin: > http://maven.apache.org/plugins/maven-dependency-plugin/ > I've read docs and see this: ---------- <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> ----------- I wonder if it means every dependency to be copied should be write by hand in such way. I hope to be wrong because I found this totally ilogical. I want something to do the job automatically and not complicate the verbose maven pom configuration. Thanks in advance J J -- View this message in context: http://www.nabble.com/jar-with-dependencies-in-a-folder-tf3644333s177.ht ml#a10188383 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
