If jakarta-commons and jakarta-commons-sandbox decide to abandon Ant based builds, then you're going to need someone else to volunteer to run the nightly builds. That may not be a bad thing on its own merits (it should really be running on supported Apache hardware instead of my Linux desktop), but I'm not going to have time to deal with the intricacies of Maven for this particular purpose.
Craig McClanahan On Wed, 22 Sep 2004 08:45:23 +0100, test <[EMAIL PROTECTED]> wrote: > I'm a Maven newbie (though I generally like it), but I agree totally. I > really think that all projects should support Ant and Maven. I would hate to > lose the ability to go down the Ant route whenever I want/need to. Again, I > like Maven, but I generally find Ant much less problematic - probably down > to my lack of experience with the tool. > > Cheers, > Rory > > > > > ----- Original Message ----- > From: "Mark R. Diggory" <[EMAIL PROTECTED]> > To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> > Sent: Tuesday, September 21, 2004 4:43 PM > Subject: Re: [general] Do we need to support Ant based builds? > > > Again, its important that a Commons project support both ant and maven. > > Use the project template directory to build new projects, maven is > > required to build your sub-projects site, I recommend that new projects > > use Maven's ant build.xml generation task to maintain the projects > > build.xml, this build.xml contains tasks that are used by Craigs nightly > > build script to generate the nightly snapshot. Legacy projects that have > > their own ant build.xml files are just fine and should continue to be > > maintained. > > > > We should use both routes. > > > > -Mark > > > > Eric Pugh wrote: > > > Okay.. well, it sounds like the consensus is that Ant support is a Good > > > Idea, so we'll keep it.. I'll play around with adding the Ant > generation > > > task to maybe our maven site goal so that we keep it up to date.. > Mostly > > > it's just an issue of keeping the script up to date with the Maven > build.. > > > Dependencies seem to get out of sync quite easily! > > > > > > Currently, the build is quite simple, and the maven ant plugin works > fine > > > for everything, so we'll keep it up to date! > > > > > > Thanks for all the feedback! > > > > > > Eric > > > > > > > > >>-----Original Message----- > > >>From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > >>Sent: Tuesday, September 21, 2004 11:17 AM > > >>To: [EMAIL PROTECTED] > > >>Subject: Re: [general] Do we need to support Ant based builds? > > >> > > >> > > >>On Tue, 21 Sep 2004, Dion Gillard <[EMAIL PROTECTED]> wrote: > > >> > > >> > > >>>C'mon, that one doesn't even run tests! > > >> > > >>8-) > > >> > > >>At least it has a bunch of dependencies, that's what non-trivial meant > > >>in my mail. > > >> > > >><http://brutus.apache.org/gump/public/db-commons-sandbox/db-common > > >>s-grafolia/gump_work/build_db-commons-sandbox_db-commons-grafolia.html> > > >>does run unit tests. > > >> > > >>Hmm, in > > >><http://brutus.apache.org/gump/public/excalibur/excalibur-thread-i > > >>mpl/gump_work/build_excalibur_excalibur-thread-impl.html> > > >>the unit tests fail to compile even though the project lists a > > >>dependency on JUnit, while Grafolia (which works) does not declare > > >>such a dependency. > > >> > > >>We really need help from people who understand Maven better than I do > > >>to take the final steps. It seems we are pretty close. Want to come > > >>over to [EMAIL PROTECTED], Dion? > > >> > > >>Stefan > > >> > > >>--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > > Mark Diggory > > Software Developer > > Harvard MIT Data Center > > http://www.hmdc.harvard.edu > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
