Hi Pier,
> >
> > 1. Tomcat documentation sucks :-)
>
> +1
>
> > 2. There needs to be a new CVS project called jakarta-tomcat-doc.
>
> Strong -1. Tomcat 3.x and 4.x have just one thing in common right now. The
> friggin' servlet spec (and not even that since between the two
> versions they
> implement there is _quite_ a difference).
>
> All the rest is different, from how you build them, to how you configure
> them, to the "technical" aspects of it...
>
> And being so different, I strongly believe that the documentation
> should be
> on two different separate CVS trees, as the two "versions" are on two
> separate CVS trees...
Maby there is a big difference between the versions of tomcat (installation
etc), but from my point of view the ideal world (which we all want) is the
documentation combined together. (I'm talking my situation here and didn't
do a survey or something). I use almost all the tomcat versions available
and when necessary I have to drag the documentation from everywhere to see
what a certain version was all about to install etc. I don't think I'm the
only one who uses jserv, tomcat 3.1, tomcat 3.2, tomcat 3.2.1 tomcat 3.2.2,
tomcat 3.3 and tomcat 4.0 (ehh the last one isn't used very much yet..). All
servers have different versions and also for different reasons. To keep
track of all the versions is hard enough as it is, so regurarly updating the
docs for all tomcat versions from the cvs tree is an ideal scenario for me.
Having more and more cvs trees is also getting a little bit confusing.. Also
a lot of people are upgrading from a version to a version, so you want to be
able to compare settings with other versions easily, without checking out a
certain branch etc,etc.
So my vote (if it counts), is one big (organized!) bucket of docs..
Hope my input is any usefull.
Mvgr,
Martin van den Bemt
