On Fri, Apr 11, 2014 at 5:29 PM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > On 11 April 2014 22:10, Benson Margulies <bimargul...@gmail.com> wrote: > >> > >> > Fwiw, I don't recall the dependency plugin actually injecting stuff into >> > the project class path but equally wish that the copy/unpack goals could >> > simply go away regardless. (in leu of the more normal xxx-dependencies >> > versions) >> >> If you make them go away, please find them a new home. I use them >> constantly to unpack data resources retrieved from a Maven repo. It >> seems odd that they live in a 'dependency' plugin, but it would be a >> disaster if they disappeared. >> > > You should be declaring the resources you are unpacking/copying as > dependencies and then using the copy-dependencies or unpack-dependencies > goal instead of the copy or unpack goal.
I don't want them in the classpath. Even if their filenames end in '.jar'. > > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
