bendg wrote: > > Hi Jorg, > > Thanks for your reply. > > Is there a nice work around for this? I was thinking binding a > ant-run-plugin with all > deps at top level pom, and call empty build.xml ?
Use a common parent POM and declare a pluginMgmt section the antrun plugin with the version and all necessary deps you might need in your builds. Note, that the same problem may arise if you use a different plugin that declares a dependency on th antrun-plugin. This is the reason why nobody should derive from existing plugins (especially since then you might even get a wrong version of the plugin). > Also, this feels like a bug, is it likely to be fixed or worth raising? No, it's a well-known classloader issue that can be addressed only in future version of Maven. AFAICS the situation is better in M3, but I don't know the exact status. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
