>The main document still covers mod_jserv, the mod_jk document is a
>separate HOWTO, there's no mod_webapp coverage, the procedure for
>mod_jk.conf-auto has changed a few times, the instructions for NT and
>Unix are kind of jumbled...
We're working on JTC having an easy to build mod_jk, via autoconf,
allowing you build it dynamic (DSO) or static.
Also works is on progress to have an uniq configuration file,
which should be used on Apache1.3/2.0/IIS/Domino/iPlanet.
>>Correct me if I'm wrong, but the changes I made to the User's
>and Apache
>>guide like the biggest two (and only two major) changes in
>the docs since
>>Gal originally wrote them? Hell, that was last summer...
>just goes to show
>>how everyone likes to talk about docs, but no one actually
>DOES anything.
There wasn't much change in mod_jk since last year, many bugs fixes
and a only one new directive JkLogStampFormat, which specify the time-stamp
to be used on log. And yes I didn't comment it in mod_jk-howto.html found
in TC 3.3.
3.2.x is closed to new features, so the Log Stuff was added only in TC 3.3.
Up to JTC startup, we were in a stupid situation where the latest mod_jk,
with added features like TS in log or Apache 2.0 support was only present
in 3.3 even if TC 3.2.2 users could use it. Only in mod_jk area, we have
2 branches of documentation to maintain :(
That's why I strongly think documentation should be uniq, with remarks/tags
to about new features.
Another arguments for a common documentation is that there is 3 tomcat
branches 3.2/3.3/4.0 and users from one versions could detect and reports
erratas in docs which would be profitable to all readers....
