Like Maven itself, scope has just one value and it is somewhat
hierachical. It's hard to run without your compile-time dependencies,
so it includes those. test includes them all.
What is the use case for separating them out?
- Brett
On 10/11/05, David Pick <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I
I guess I could write my own dependencies task and scope filter.
Regards
Dave
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 11 October 2005 14:15
To: Maven Users List
Subject: Re: [m2b3] Ant Dependencies Task and Scope
Like Maven itself, scope has just one value
On 10/11/05, David Pick <[EMAIL PROTECTED]> wrote:
> I do not need the artifacts required for compilation as they are provided
> automatically by the runtime container, so I thought I could define "runtime"
> dependencies and just resolve these.
There is actually a "provided" scope for this purp
orter [mailto:[EMAIL PROTECTED]
Sent: 11 October 2005 14:57
To: Maven Users List
Subject: Re: [m2b3] Ant Dependencies Task and Scope
On 10/11/05, David Pick <[EMAIL PROTECTED]> wrote:
> I do not need the artifacts required for compilation as they are provided
> automatically by the runtime
