What about (ab-)using the runtime scope for this? The core could inspect the pom and inject runtime dependencies into the class path.
Regards Mirko -- Sent from my mobile On Apr 12, 2014 2:08 PM, "Hervé BOUTEMY" <[email protected]> wrote: > after thinking more at it, it seems the "scope" for such artifacts is the > plugin parameter name > > so why not resolve artifacts (or collections of artifacts) when injecting > parameters? > I'm not sure we really need a need elemen in pom. > > Regards, > > Hervé > > Le samedi 12 avril 2014 10:14:51 Robert Scholte a écrit : > > Op Fri, 11 Apr 2014 23:50:54 +0200 schreef Benson Margulies > > > > <[email protected]>: > > > On Fri, Apr 11, 2014 at 5:29 PM, Stephen Connolly > > > > > > <[email protected]> wrote: > > >> On 11 April 2014 22:10, Benson Margulies <[email protected]> > 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'. > > > > The current proposal is to add an artifacts-element[1] to the plugin. > > Dependencies are for the classpath, artifacts are additional files which > > must be resolved, but don't belong on the classpath. > > > > Robert > > > > [1] > > > https://cwiki.apache.org/confluence/display/MAVEN/Resolution+scenarios+for+p > > lugins > > >>> --------------------------------------------------------------------- > > >>> 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] > >
