I did do a little looking around 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 Subject: 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 > <optional>true</optional> 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 my own project > build, and therefore the compilation fails. > > ..David.. > > > --------------------------------------------------------------------- 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]
