We already have eclipse files checked in AFAIK - that counts as the second build system. We used to have makefiles too, also in parallel with ant (in 3.0 times).
The goal IMO is that people who like to type mvn can do it - without any guarantee that the result will be identical with the official release or will be maintained long term, just like the eclipse project can run but it's quite different from the official build. If it's making easier for some people to build tomcat - and it doesn't affect people who use ant in any way - what's the harm ? Costin On Wed, Apr 30, 2008 at 2:23 AM, Remy Maucherat <[EMAIL PROTECTED]> wrote: > On Tue, 2008-04-29 at 22:28 -0400, Yoav Shapira wrote: > > On Tue, Apr 29, 2008 at 10:09 PM, Remy Maucherat <[EMAIL PROTECTED]> > wrote: > > > The current build scripts are fully tested and work well. Adding > > > additional methods of building or replacing these scripts altogether > > > would only provide ways to create and/or release broken binaries. > > > > Again, no one is saying anything about touching the current build > > scripts, build process, release process, or source structure. All > > those remain the same. The job of the release manager remains the > > same. > > > > This is just an alternative for those people who want to use a > > slightly easier / user-friendlier build system. We could do worse > > than lowering the barrier to entry for new contributors. > > You mean you type "mvn" instead of "ant" ? I agree te keys are closer > together on my keyboard, so it could indeed be easier. Personally, I did > have a first hand experience with Maven, and I think it's horrible (you > have no clue what it is doing, error reporting is bad, and basically, > you have to think and act the tool's way). > > I disagree with having two separate build systems, there's no guarantee > of equivalence. > > Rémy > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
