>>>>> "Ted" == Ted Husted <[EMAIL PROTECTED]> writes:
Ted> The API part is automatic. There's a stylesheet for the taglibs that lets Ant
do all the work. =:0)
Ted> The other part is the package.html file, which the JavaDoc automatically
bundles in as the "description" portion
Ted> on the cover page for the package
Yes, the API part is automatic, for the "struts-*.xml" files in the main Struts
distribution, which also generates the TLD files. The "struts-*-el.xml" files
for Struts-EL are in "contrib/struts-el". How do we automatically generate the
API documentation for Struts-EL so it is inserted into the user guide in the
main distribution?
Similarly, we'll have to figure out what to do about the javadoc for Struts-EL.
Ted> So, for the narrative you mentioned, follow the example of the other
package.html files
Ted> (taglib/bean/package.html), and it will be compiled into the JavaDocs.
Ted> Once that is done, I can setup the rest of the Struts-EL Developer guide, if
you like.
That would be fine.
Ted> Pzst 1.1, I'd like to try and do more of the "Developer Guide" kid of thing,
and link more into the JavaDocs.
Ted> Right now, we're getting into a lot of dual maintenance. But first things
first.
I'm not sure what you mean here.
--
===================================================================
David M. Karr ; Java/J2EE/XML/Unix/C++
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
