+1

A couple of minor points below...

> Attached is my previous file which documents the current jakarta-taglibs
dir/file
> layout and build process.  Included at the end is my proposal for a new
> dir/file layout and build process.
>
> Comments?  Votes?


> Configuration Files (taglib-doc-kit)
> ------------------------------------
>
> <taglib>/xml/<taglib>-tags.xml - Taglib and tag XML data transformed by
taglib-doc-kit/xml/taglib-doc.xsl into the taglib index.html documentation
and by taglib-doc-kit/xml/tld.xsl into the <taglib>.tld

I've been using the pattern

    <taglib>/xml/<taglib>.xml

(i.e. without the trailing "-tags") in the IO, Log and XTags libraries. Is
this a problem or can we relax the restriction? I'm happy to go either way
on this.


> Build Files
> -----------
>
> .cvsignore - CVS file specifying what files to ignore, add build, dist,
and build.properties


Cool!

> build.properties.sample
>
>    Example build properties file used to configure ant properties for
required jar files.
>    The jar file properties will be in the form "servlet.jar=<path to jar
file>",
>    version specific jars would be "servlet-2.2.jar=<path to jar file>.
This means that
>    the build.bat and build.sh scripts can be removed. $ANT_HOME/bin would
have to be
>    in your PATH so that you could build by using "ant dist".

Cool - like it.

> build.bat - Windows build script: Remove, no longer needed
> build.sh - Unix build script: Remove, no longer needed
> build.xml - Overall taglibs Ant build config
> common.properties - common properties for building a taglib
> common.xml - common Ant config for building a taglib:
>
>    Switch common.xml from using env vars for jar files to using
build.properties.

+1

>    Add the ability to generate documentation using the new taglib-doc-kit.

I've already added the gen-doc target to the common.xml so that any task
that depends on the gen-docs target gets this stuff for free. Its all in use
in IO, Log and XTags right now.

I've no idea where the <taglib>-tags.xml files are for all the other
libraries. I assume people have been creating the HTML and TLD by hand up to
now? Maybe we can reverse engineer them all via XSLT then add the
documentation back in by hand?

Great piece of work Glenn.

James


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Reply via email to