I'm using the unpack goal in the depenency plugin. Somehow I got the idea that it was better to declare the thing I am unpacking as a dependency (even if I don't want it in the classpath) instead of just giving the other unpack goal a full GAV.
On Mon, Aug 2, 2010 at 1:34 PM, lukewpatterson <[email protected]> wrote: > > > Benson Margulies wrote: >> >> process it in the dependency plugin. >> > > what do you mean by "process"? if you mean "copy" or "unpack", m-d-p [1] has > separate goals for working with artifacts listed in the configuration > section and working with project <dependency>s > > e.g. see "copy" [2] vs. "copy-dependencies" [3] > > [1] http://maven.apache.org/plugins/maven-dependency-plugin/ > [2] http://maven.apache.org/plugins/maven-dependency-plugin/copy-mojo.html > [3] > http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html > -- > View this message in context: > http://maven.40175.n5.nabble.com/A-dependency-only-for-the-dependency-plugin-tp2261982p2262028.html > 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]
