You want me to help you go down the wrong path? :-) Don't have the code here (customer closed source), but I believe I saw it first in some other plugin. Have a look in JBoss's ws maven plugin: http://anonsvn.jboss.org/repos/jbossws/projects/plugins/maven/jaxws-tools/trunk/src/main/java/org/jboss/ws/plugins/tools/AbstractToolsMojo.java Look at how the classloader is created. I *think* this is what I did (or something similar).
I'd like to stress the problem with forcing a Maven project to add dependencies it shouldn't have. It's just plain wrong. /Anders On Thu, Aug 2, 2012 at 11:20 AM, Jochen Wiedmann <jochen.wiedm...@gmail.com> wrote: > On Thu, Aug 2, 2012 at 10:58 AM, Anders Hammar <and...@hammar.net> wrote: >> What I have done in a customer specific plugin, is to not have a >> dependency on some library in the plugin itself but rely on it being >> declared as a dependency in the Maven project where the plugin is >> bound. That made it totally controllable by the project. > > Sounds exactly like what I intend. Could you share some lines of code, please? > > > > > -- > In other words: what could be seen as a socially debilitating failure > of character can certainly work to your advantage too. (Linus > Torvalds, but the use in the signature tells something about me as > well.) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
