maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Fox <bri...@infinity.nu>
Subject Re: [Maven 4.0.0] Removing ability for plugins to dynamically inject dependencies
Date Sat, 12 Apr 2014 01:47:52 GMT
On Fri, Apr 11, 2014 at 5:50 PM, Benson Margulies <bimargulies@gmail.com>wrote:

> On Fri, Apr 11, 2014 at 5:29 PM, Stephen Connolly
> <stephen.alan.connolly@gmail.com> wrote:
> > On 11 April 2014 22:10, Benson Margulies <bimargulies@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'.
>
>
Well, that is the use case I had when I created them originally. I just see
too many people abuse these when they simply could have used the
-dependencies versions just as effectively and with better compatibility to
other plugins.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message