Hi Costin, Costin Caraivan wrote: > > justinedelson wrote: >> >> You need to add dependencies to the plugin, not your project. >> > > I added them to the plugin (#1), to the project (#2), to both (#3). It did > not work in any case. I found a workaround, it's a bug in the antrun > plugin. If you have multiple poms using the antrun plugin, the classpath > isn't reset.
This is not a bug of the antrun-plugin, it's the way Maven 2.0.x works. Use a common parent with a pluginManagement section where you define all ant deps of all POMs where you use antrun. > So you need to set it right the first time, to make sure it > works currectly. The pluginManagement can help. > Using ids and such, as recommended here, didn't work (so the bug is still > there): > http://jira.codehaus.org/browse/MANTRUN-51 No, since Maven will load the plugin once and only. After that the classpath is fixed. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
