On 17/11/2011, at 9:46 AM, Chuck Hill wrote: > On 2011-11-16, at 2:26 PM, Hugi Thordarson wrote: > >>> Ant is pretty simple. Mostly I don't even think about the Ant portion of my >>> WO projects other than to tell Hudson that it has to issue an Ant command >>> to build the project. >> >> Before you can even think about building WO projects using Ant you have to >> at least have woproject.jar in your Ant plugin classpath. And then, the only >> reason you don't think much about Ant is that Someone Else wrote a >200 line >> Ant script for you (that you are required to copy verbatim for each and >> every WO project you create. How's that for reusability). > > As opposed to copying and editing a pom.xml?
When would you do that? Usually you would create a project from a template (called an archetype in maven speak). i.e., just use Eclipse maven wizard. >> The initial setup of a Maven environment for WO development may take an hour >> or two—that's because WO is proprietary and thus requires some installation. >> But once your environment is properly set up, Maven works great. I started >> out the easy way—just added a "pom.xml" to my standard frameworks alongside >> the "build.xml"-files (like Project Wonder does). But eventually, you'll >> want to use all the amazing features Maven has to offer. > > Like having to edit each pom when you make a new non-SNAPSHOT version? Again, when would you do that? I've never seen that happen. You use the maven release plugin. "Look Ma! No hands!" >> And it's so much simpler than the 200+ lines of procedural code every single >> simple little WO application requires to even build with Ant. > > But you don't have to mess with that. Perhaps. Lachlan Deck [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
