The latter. See http://maven.apache.org/plugins/maven-antrun-plugin/examples/customTasks.html for the syntax.
On Aug 25, 2010, at 8:35 PM, Jacob Beard <[email protected]> wrote: > Hi, > > Thanks for the reply. > > I'm brand new to Maven, and so I don't quite understand what you mean. Are > you saying that the antrun plugin itself should include these libraries as > dependencies; or is it possible, in my project, to inject new dependencies > for specific plugins, beyond what they specify on their own? > > Please let me know. Thanks, > > Jake > > On 10-08-25 08:01 PM, Justin Edelson wrote: >> Shouldn't these just be dependencies of the antrun plugin instead of >> your project? >> >> On 8/25/10 7:23 PM, Jacob Beard wrote: >> >>> Hi, >>> >>> I've just read the Introduction to the Dependency Mechanism document: >>> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html >>> >>> >>> My project still relies heavily on Ant for building, but I'm migrating >>> to Maven for dependency management, among other things. >>> >>> There are several libraries that are used in my project's Ant build >>> script, but not in the application itself. Examples of these include >>> ant-contrib, bean scripting framework, and commons-logging. I'm >>> wondering, what Maven dependency scope is most appropriate for these >>> kinds of dependencies? It seems tricky, because these dependencies are >>> required for neither compilation nor execution of the project's source >>> code, but are instead required for executing the build script. >>> >>> Let me know what you think. Thanks, >>> >>> Jake >>> >>> --------------------------------------------------------------------- >>> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
