Well, have you read the documentation? I never used antrun myself, but it seems like you have to expliticitly reference the classpath if you want to use non-standard tasks. Adding dependencies is just the first step. The second step is to use classpathref="maven.plugin.classpath", see http://maven.apache.org/plugins/maven-antrun-plugin/examples/customTasks.html
<http://maven.apache.org/plugins/maven-antrun-plugin/examples/customTasks.html> Cheers 2010/3/9 bendg <[email protected]> > > I forgot to say, I have run with -X and -e and the dependencies do not > appear > in the trace, which I assume means the dependencies are not being attached > to the new classloader that is created when the plugin runs. This is > consistent with the behaviour I am seeing too.... > > > -- > View this message in context: > http://old.nabble.com/Antrun-plugin-reg-exp-tp27833419p27835663.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
