You can try the following ...
project
xmlns:deploy=deploy
xmlns:ant=jelly:ant
goal name=get-deps
deploy:copy-deps todir=${basedir}/lib/
/goal
preGoal name=runtest
attainGoal name=get-deps/
/preGoal
goal name=runtest
ant:ant dir=${basedir} antfile=build.xml
Hey Feilpe
Yes, you can, as long as they are ant 1.5 compatible, no problem.
I personnaly migrated a lot of Ant legacy code to a new maven.xml and it
did workout nicely.
Hope it helps.
Eric.
Feilpe Vieira Silva wrote:
Dear members,
I have an ANT build.xml files, with several well tested tasks
All Ant tasks are first class citizens in Maven. So when maven does a
copy/ it is using the Ant copy task. For examples on scripting in Maven,
look in maven-plugins in CVS. Look for ant: to find lots of examples.
Here's an article about writing a plugin, which is representative of writing
a
Hi Feilpe
Using ant within maven is relly simple:
for example:
ant:copy todir=${maven.build.dir}/${project.id}/WEB-INF/classes
ant:fileset dir=${dir.project}/src
include name=**/*.xml /
/ant:fileset
/ant:copy
just use the ant namespace prefix
Thank you all for the frindly support.
The issue is about culture of my project members. My new project is
growing up very quick and now we have several members expert in ANT
and some members optimist about MAVEN (including me). I need arguments
to convince these people about the gain in using
