Hi,
My motivation to use Maven comes from the fact that I'm working on a
Commons sandbox component. Because all of Commons build infrastructure
is Maven-based, there's a strong incentive for me to integrate my
project with Maven. So, basically, I'm trying to have the best of both
worlds: to reuse the work I've done with Ant, while leveraging all that
Maven and the Commons parent pom bring to the table.
I really don't see why, in principle, hooking into Ant with Maven and
AntRun is a bad idea. I think it's fairly common for build systems to be
made extensible through multiple mechanisms, including both plugins and
scripting. I see AntRun as bringing a scripting language to Maven, which
is an alternative to extending it with plugins. As my project is quite
different from a typical Maven project, I feel that it is appropriate to
start with this approach.
In any case I found the solution to my original question here:
http://docs.codehaus.org/display/MAVENUSER/Antrun+Plugin#AntrunPlugin-PassingyourMavenclasspathtoAnt:
Thanks everyone for your insight and support,
Jake
On 10-08-27 06:21 PM, Stephen Connolly wrote:
If you 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" then I recommend that you do not use
Maven. Instead use maven-ant-tasks to interact with the maven repository
and keep your build in ANT.
The reality is that if you are not prepared to drink the Maven kool-aid (it
tastes great) then stick with ANT.
The golden rule is "If a build ain't broke, don't fix it"
Now this triggers a question.... why do you want to use Maven to build your
project?
-Stephen
On 27 August 2010 17:58, Jacob Beard<[email protected]> wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
