for an issue, but didn't find one.
> Do you have any helpful terms to search on that would narrow the field
> a bit?
>
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 21, 2005 2:45 PM
> To: Maven Users List
>
x27;t find one. Do
> you have any helpful terms to search on that would narrow the field a
> bit?
>
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 21, 2005 2:45 PM
> To: Maven Users List
> Subject: Re: [m2] Is this correc
t: Re: [m2] Is this correct behavior for optional dependency?
I think this may have been fixed in 2.0.1 - check JIRA for an existing
issue first.
On 11/22/05, David Jackman <[EMAIL PROTECTED]> wrote:
> Based on my reading of the docs and the mail archives, adding
> true to a depende
I think this may have been fixed in 2.0.1 - check JIRA for an existing
issue first.
On 11/22/05, David Jackman <[EMAIL PROTECTED]> wrote:
> Based on my reading of the docs and the mail archives, adding
> true to a dependency should affect other projects
> that depend on my project, but not affect
You are right, could you please file an issue and attach an use case
where it doesn't work?
On 11/21/05, David Jackman <[EMAIL PROTECTED]> wrote:
> Based on my reading of the docs and the mail archives, adding
> true to a dependency should affect other projects
> that depend on my project, but not
Based on my reading of the docs and the mail archives, adding
true to a dependency should affect other projects
that depend on my project, but not affect the building of my own
project. Is that true? Right now, I'm seeing otherwise. If I mark a
dependency as optional, then it's not included in m
