The dependency of the plugin will be in the classloader of the plugin already - you don't need to do anything else. You can use mvn -X ... to see the full construction of your plugin for more information.
Or are you trying to dynamically use a dependency of the project the plugin is operating on? On 19/02/2010, at 3:26 PM, Kai Hackemesser wrote: > Hi there, > > I'm writing my first plugin. My plugin will have a dependency to another > library/artifact that needs to be added to the classpath when the plugin > executes its work. How can I find the artifact that the plugin is depending > to, when the plugin is running? The maven-dependency-plugin resolves the > dependencies of the current project, not of the current plugin. Or am I > wrong here? > > Cheers, > Kai -- Brett Porter [email protected] http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
