Unfortunatly, I won't be able to participate much in this discussion this
weekend since i know *0* about AWT and the Java cert (Monday morning, 9am)
apparently thinks you should =) Sorry all...
> The important issue is *not* what transformation tool is used. The
Oh, by "works for Catalina" I was stating that TC4 is already using the
tool; why not continue using it?
> * Docs should live in the source tree of the project that they
> are about. Although Henri's suggestion for jakarta-tomcat-docs
> is noble, what you'll find in practice is that there is very little
> documentation that is relevant across multiple versions of Tomcat.
I have a feeling that whatever is the same will be a lot of piecemeal here
and there, excluding of course, web-app documentation. So far yourself,
Pier, and Henri are the only three TC developers to post their position on
that (re: inter-version relevancy). Personally, I don't think there should
be a separate project, but I think I've already said that a few times =)
> * The files that are checked in should only be the XML sources, *not* the
> generated files. This varies from what Jon set up in jakarta-site2,
> based on long and drawn out earlier discussions (same issues as those
> surrounding checking JAR files into CVS :-).
Someone will have to setup something that exposes the latest generated
documentation on the Jakarta www site. It's being done already for Struts,
so I guess that won't be a big problem.
> * At least two documentation webapps (developer-oriented and
> user-oriented) would seem to be appropriate. Having more than two
"developer" as in "web" or "Tomcat"? I'm not sure why separating the doc
into two packages helps - perhaps I'm missing some obvious benefit trying to
think at 7:15am =)
- r
