Thanks for the quick answer. I am not not 2.0.5 yet but I assume
you mean any version of 2.0.x will not work. So that means there is
no way to do a taskdef in an ant based mojo? I could have sworn I
had it working a few months ago. Seems that an ant mojo is pretty
hampered if I cannot define any taskdefs. I guess I will have to see
about using a Java mojo to front end the ant tasks and then use the
java mojo facilities to create the task def. I was hoping someone
had come up with a cute trick to allow tasks defs in ant based mojos.
Too bad as it would have made it an easy task to implement the ant
tasks I need and to front them with mojos for ease of configuration.
I will keep my fingers crossed for a solution soon but in the mean
time I guess it is slog in the code again time.
Scott Ryan
On Feb 17, 2007, at 7:42 PM, Jason van Zyl wrote:
On 17 Feb 07, at 4:54 PM 17 Feb 07, Scott Ryan wrote:
I am trying to write a very simple Ant based script mojo. I need
to define some taskdefs from within the build.xml based on the
current classpath defined in the plugin pom. I have seen
reference to using the maven.plugin.classpath but when I reference
that I get an error that it is not present. I also tried passing
the path in as a parameter to the mojo but that did not work
either. The basic idea is that I have an Ant based mojo and I
want to define a taskdef in my build.xml based on the classpath
defined in the pom.xml of the plugin.
Any ideas or suggestions would be appreciated.
This will not work with 2.0.5. I have made changes to 2.1.x that
allow using file references and the classpath information (just
like the ant-run-plugin) but I currently have not merged it back to
2.0.x.
Jason.
Scott Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
