Question: WHAT THE HECK IS ANT?
Now I know what ant is, I'm just hyperbolizing. But...
It's just that I got the entire Tomcat 3.1 tree to compile with a single
Makefile in around 10 minutes. I can't figure out what Ant is helping this
project with. Maybe I'm just stupid or something but this Ant thing
doesn't really impress me very much. Make is very stable, very cross
platform; I just don't see what's so cool about ant.
Why is ant better than Make?
And don't say "ant is cross platform, make is not" because that just isn't
true. Was someone just bored with the wheel and wanted to reinvent it?
I just want to understand.
Thanks.
-Nick
On Fri, 3 Nov 2000, Pier P. Fumagalli wrote:
> Question: WHAT THE HACK IS TOMCAT 3.3 ???
>
> I believe that this developer community once agreed that Tomcat 4.0
> _will_be_ the next major release of the Apache Software Foundation servlet
> engine, but, since a couple of weeks, I see a proliferation of emails
> talking about Tomcat 3.3.
>
> Here is where I'm getting confused... When did we vote about having a dual
> codebase for two different servlet engines at the same time??? Because I've
> never seen such a discussion taking place...
>
> Also, it seems ridiculous (at least to me) to start talking about what will
> be the next release of the 3.x tree (3.3) when 3.2 is not yet out of the
> door, and as far as I've read (but I might have missed some emails) Beta-6
> is not even compiling...
>
> Sorry, but as a long time ASF member, and one of the first kids involved in
> the glorious JServ, I feel that things here are getting a little bit screwed
> up. Are we going to screw our release cycles? Are we going out to the public
> with TWO servlet engines equal in features, but different in codebases? Are
> we all going NUTS?
>
> Sorry again, but this time I have to vote -1 on a "new" Tomcat 3.3,
> expecially before 3.2 final is out of the door. The NEXT major release is
> going to be Tomcat 4.0, based on Catalina, as we all agreed on months ago.
>
> But, I'm not _only_ a pain in the ass... I see there are some developers who
> prefer to work on the 3.x tree, rather than helping out on the 4.0, so,
> instead of cutting their wings and forcing them to fork the project, I
> propose to them what was proposed to Craig in february.
>
> The "Rules for Evolution and Revolutions" still stands still, as one of the
> major constitution documents for this community (James, WTF, post it
> somewhere!!! :) and IMNSHO needs to be used...
>
> I suggest to whoever is interested in further developement of the 3.3 tree
> to create a new proposal, as Craig did with Catalina, and stick it on the
> "proposals" directory in the CVS. And start working from it. I'm more than
> open to see, after Tomcat 4.0 sees light, to reconsider the effort, and
> maybe switching codebase again for what will be Tomcat 5.0.
>
> So, I'm proposing this plan, and please vote on 2 and 4 (1 and 3 were
> already voted upon with a bunch of +1s)...
>
> 1) Release Tomcat 3.2 final (soon, please!)
> 2) Create a new proposal tree alongside with Catalina (new name to avoid
> confusion, please)
> 3) Release Tomcat 4.0 (with Catalina, as we all decided)
> 4) Decide wether Tomcat 5.0 will be Catalina based or "whatever" new
> proposal comes along.
>
> My 0.02 $... Take care...
>
> Pier
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Nicolaus Bauman
Software Engineer
Simplexity Systems
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
