On the nightly stuff; I think Gump can do Maven builds now, rather than the ant scripts, and if not, I've got a (probably quite similar to Craig's) build system set of scripts for Maven that we could use.
Hen On Mon, 20 Sep 2004 13:44:54 -0700, Martin Cooper <[EMAIL PROTECTED]> wrote: > On Mon, 20 Sep 2004 12:11:22 -0400, Shapira, Yoav <[EMAIL PROTECTED]> wrote: > > > > Hi, > > It should be a project-by-project decision. > > That would be ideal, IMO, but I don't think it's what you mean. ;-) I > think you mean component by component. It would be nice if we could > say that the entire Jakarta project uses a unified build system, but I > doubt that'll ever happen. ;-) > > -- > Martin Cooper > > > > > > If someone wants to dump > > Ant and require Maven for building, or vice versa, it's their decision. > > So for Configuration, you and the other active developers should decide. > > > > I personally use Ant and don't like Maven too much. I think the Ant > > user base is wider than the Maven one based on how long the two have > > been available. Ant's the closest thing there is to a de-facto building > > standard in the Java world pretty much. So if a project decides to > > require Maven and not support Ant for building, I think you'd limit your > > user base. But as I said, that's a decision for the project's > > developers to make. > > > > I wouldn't like Commons to require Maven for all the Commons projects > > for the above reasons. > > > > As an aside, I thought Maven was capable of generating an Ant build > > file? Is that buggy or something? > > > > Yoav Shapira > > Millennium Research Informatics > > > > > > > > > > >-----Original Message----- > > >From: Eric Pugh [mailto:[EMAIL PROTECTED] > > >Sent: Monday, September 20, 2004 11:42 AM > > >To: Commons-Dev > > >Subject: [general] Do we need to support Ant based builds? > > > > > >Subject says it all. For configuration we use Maven to perform the > > build.. > > >And frequently we get questions from people using the Ant based build, > > >which > > >we seem to be pathologically incapable of keeping up to date... > > > > > >I am trying to go come up with solutions like: > > >1) Rebuild the ant build.xml as part of the normal build process > > >2) Do funky logic to detect if the ant build.xml is out of date w/ the > > >maven > > >process > > > > > >However, if we could just say "use Maven" then things would be much > > >simpler. > > >While I don't want to come across as a Maven zealot or providing bad > > >customer service to all the Ant users, having the two build systems > > leads > > >to > > >lots of problems for Ant users... > > > > > >Eric Pugh > > > > > > > > >--------------------------------------------------------------------- > > >To unsubscribe, e-mail: [EMAIL PROTECTED] > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > This e-mail, including any attachments, is a confidential business communication, > > and may contain information that is confidential, proprietary and/or privileged. > > This e-mail is intended only for the individual(s) to whom it is addressed, and > > may not be saved, copied, printed, disclosed or used by anyone else. If you are > > not the(an) intended recipient, please immediately delete this e-mail from your > > computer system and notify the sender. Thank you. > > > > > > > > > > --------------------------------------------------------------------- > > 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]
