Hi Luis, As you'd already know, Maven is good with the following, a) maven is structured and more declarative (less procedural) than Ant. b) maven manage your dependencies properly (or at least in its ideal) c) maven can generate IDE project files easily d) life cycle management ensure that test cases and other important things always run e) central repository of artifacts with maven corrdinates.
All of those should add up to simply, less pain and more elegant way in managing build. But gotcha that I found are a) single artifact per module (generally ok but occasionally you need to do some trick with dependency plugin to import source/resources from another module). b) It's not as robust as Ant - expect to find critical bugs and things that you need to work around. c) version range is still buggy. d) can be very verbose if you want to ensure that your build is repeatable - you need to explicitly declare every plugins in the root pom. e) different settings.xml can lead to different build results. different local repository can also lead to different build results. Obvious, but it means that your maven project depends on these external factors and you'd often find youself flushing local repo when things doesn't work right. f) You need to understand how to develop convention for groupId and artifactId and their impact. Ideally, artifactId needs to be a unique id irregardless of groupId that it belongs to. I find that groupId is not really like a qualifying package name, it's more of a unique project id that should be the same across muti module projects. g) Plain old maven repo can get corrupted if there are concurrent deployment. Is it worth it? I think so but won't be a painless experience! Cheers, rOnn c. "Luis Roberto P. Paula" <[EMAIL PROTECTED]> 12/11/2007 12:14 AM Please respond to "Maven Users List" <[email protected]> To [email protected] cc Subject Ant to Maven Hi, I'm work in a huge java project that has a ant script with almost 800 lines. The last two weeks I'm trying to convert this script into a maven2 multiproject, in order to simplify the build process, and its being such a pain in the ass. My questions are: - Is it worth to do this? - I know it is a great software, but in what causes maven is not recommended? Thanks, Luis ###################################################################### DISCLAIMER: This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorized to copy or disclose all or any part of it without the prior written consent of Toyota. Opinions expressed in this email and any attachments are those of the sender and not necessarily the opinions of Toyota. Please scan this email and any attachment(s) for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. ######################################################################
