Hi Wayne,
The situation is that I have invested a significant amount of time in
preparing the Ant build, and so I would prefer to find a way to leverage
this work, rather than starting from scratch with Maven. As my project
is unconventional, and I'm not yet fully comfortable with Maven, I feel
like, at this stage, continuing to use Ant for certain parts of the
build is a better, safer approach. I believe this is what the AntRun
plugin is designed to facilitate.
If anyone could offer any guidance regarding my original question, I
would greatly appreciate it. Thanks,
Jake
On 10-08-27 12:17 PM, Wayne Fay wrote:
/home/jacob/workspace/gsoc2010/git-scxml-js/scxml-js/test-maven.xml:19:
Reference maven.compile.classpath not found.
Please let me know what you think. Thanks,
Is this just "for fun" or are you seriously trying to build a big mess
of your build by continuing to use various aspects of your build in
Ant via Antrun and other aspects in Maven, and then sharing properties
around etc?
Honestly, you should just convert your Ant "stuff" into Maven plugins.
It is pretty simple to write proper Maven plugins. And far easier to
debug things when it doesn't work properly.
Wayne
---------------------------------------------------------------------
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]
