To be honest, I too have my reservations towards Maven as I've been very happy with Ant, but a project the depends on volunteers such as this needs to more importantly pick one tool and use it consistently and effectively. Furthermore, this tool must be supported by those that will maintain the build. These two reasons cause me to call for Maven to be selected as the sole build tool. The turning point for me was seeing that I can embed ant tasks in the maven.xml and James' dedication to getting Maven working. As long as a new prospective developer can checkout Struts from subversion, just type "maven dist" and have the whole Struts project unit tested and built, I'll be happy.

Don

Frank W. Zammetti wrote:
I had to toy with Maven on a project a few weeks back I was asked to look at and resolve some issues with. It felt very much like using CVS to me... Gets the job done, and you know there is a lot of power there, but for a beginner it feels like its fighting you. As with most new tools, familiarity gained over time would ease the difficulty to the point, hopefully, where the power shines through and you forget your initial difficulties.

But those initial lumps stay with you a while :)

I can't comment at all on the existing Ant builds as I never had cause to compile Struts myself. If the scripts are as you say, then it certainly lessens my argument somewhat :)

As an aside, the irony here is that I wasn't thrilled with Ant at first either, but I've kind of taken a liking to it lately. For example, just last week I wrote a script that (1) stopped Tomcat (if running), (2) did some initialization tasks to prepare for the build, (3) updated a build number in an About screen JSP, (4) compiled about 200 source files, (5) compiled about 80 JSPs (to servlet and to class, just for verification purposes), (6) ran about 50 JUnit tests, (7) generated javadocs for the entire code base, (8) WARed the application, (9) deployed it under Tomcat (in exploded format, the WAR was created for manual deployment under Websphere), (10) deployed the javadocs to a documentation server, (11) cleaned up (both the build environment and deleted the Tomcat work folder) and (12) restarted Tomcat. The script to me is easy as hell to follow, doesn't require any outside configuration (you just have to update the build number in the build.xml file itself, which you are reminded about when the script is run) and runs in under 50 seconds on my 2-year old PC. I get output to the console as well as a log file too. Of course it was easy to set up for doing this (just had to add the junit.jar to the Ant folder, nothing else beyond the usual simple setup chores).

I was actually doing the same thing with a DOS batch file previously, but now I can run my build under Linux, and its a little easier to follow I think. Call me an Ant convert :)



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to