Hi, I want to be able to define some dependencies in a POM and be able to resolve them using the Ant tasks so I can incorporate them into our ant build scripts use to package up an installer/release.
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. It would also be useful if the Ant dependencies task could also be prevented from recursively resolving artifacts and only consider the POM provided. I hope this makes some sort of sense. 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 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 am trying to use the Ant dependencies Tasks to get a list of runtime > dependencies only. > > I have set the "useScope" to "runtime", however the Ant dependencies returns > both "runtime" and "compile" dependencies. Why? > > Is this a bug? > > Should "useScope" be a list of dependencies you are interested in e.g. > "runtime,compile,test"? > > Any thoughts? > > Many Thanks > Dave > > > --------------------------------------------------------------------- > 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]
