I don't believe "all but test" as a possible scope makes much sense
when you're thinking about valid use/business cases. Can you think of
such a real-life situation?

Also, it might be helpful to review the Maven Dependency Scope section
on this page:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

Wayne

On 7/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hello !
>
> I'd like to talk about the behaviour of the dependency:copy-depedencies
> plugin, when I add some include/exclude scopes parameters.
> I noticed that these parameters' types were just Strings, which means you
> can set only one include scope and one exclude scope in the config tag.
>
> After a few tests, I could establish a link between the parameter value and
> the dependencies selected. The array below describes these links :
>
> -------------------------------------------------------
> param value -> dependencies scope
> -------------------------------------------------------
> compile -> compile + provided
> runtime -> compile + runtime
> provided -> provided
> test -> compile + provided + runtime + test
> -------------------------------------------------------
>
> Fortunately, I need to get only compile and runtime, which corresponds to a
> "runtime" value in the includeScope parameter.
>
> But imagine you need "compile + provided + runtime", which is an equivalent
> of "all but test".
> How can you configure the plugin to do that ?
> If I set excludeScope to "test", the build fails because I've excluded *
> all * the dependencies.
> If I set 2 include scopes (compile and runtime), it only takes the last
> one, and doesn't work much better...
>
> Perhaps you could change the mojo's parameters to give the user more
> possibilities ?
>
> Thanks !
>
> Isabelle Guimiot
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to