>> As to whether or not it's worth it is another question. What is your motivation for performing the conversion? What problems are you currently experiencing with your ant-built process that you felt needed alleviation?
Actually, our ant-build process works fine and it is well-structured. We thought that we could incorporate some advantages from maven, such as repositories and work in a more high-level way. But nothing is too simple and wonderful like those "Hello world" examples. On Dec 10, 2007 11:20 AM, Kallin Nagelberg <[EMAIL PROTECTED]> wrote: > You may wish to start by using the maven-antrun-plugin, breaking up the > ant > into smaller files that you put alongside each pom of your multi-module > project. This way you can avoid writing all the plugins/complex poms that, > while ideal, would take more time initially. > That is the approach my project took, and we had at least 4 ant files (in > the core) with probably about 1000 lines at least. Hopefully once you go > through the process of breaking up the ant you will become intimately > familiar with it's content, and have a better idea of how much work will > be > required to complete a full conversion. > > As to whether or not it's worth it is another question. What is your > motivation for performing the conversion? What problems are you currently > experiencing with your ant-built process that you felt needed alleviation? > > > On Dec 10, 2007 8:14 AM, Luis Roberto P. Paula <[EMAIL PROTECTED]> wrote: > > > 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 > > >
