Is this the recommended approach for j2ee applications? I mean, I was thinking about switching to maven because of all the added functionalities over ant (source code metrics, cross reference source, documentation and site generation using xdocs,...) but if I have to create a maven project for each artifact in my application, I think that this could become cumbersome for large j2ee applications, so maybe I would delay adopting maven as my main build tool.
About the ant question, I have taken a look to the Turbine source, and I have noticed that provides a build.xml with target names that I have seen elsewhere. Does the target names in this file have to follow any convention in order to be used by maven? What is the relation between maven.xml, build.xml, project.xml, project.properties?
Regards Jose
Konstantin Priblouda wrote:
1. Does maven "deprecate" ant, or does maven use
ant? Must I have ant
installed in order to use maven?
It does use ant behind the scenes, but takes care of it installation itself. As well as of your dependencies
2. I have an already started project that I build
using ant. What is
the preferred way to "mavenize" this project?
The project is a
whole j2ee application, with two ejb jars and
one war. Should I
translate build.xml to maven.xml?
That's really non-trivial question. I would suggest to
start with something more simple.
Mevn projects are typically one-artifact-per-project
So you could be forced to break up your project into several pieces - for ejb tier and for web tier. And thenb build them using reactor.
Do'nt be affraid, I managed to move almost all development in our company to maven.
regards,
===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ >
__________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
