I do have the same question as James, though: Can we still generate
the TLDs from the same XML as the taglib docs? This is one place that
I got bogged down, since it seemed that Maven wouldn't take the extra
XML elements, and I would absolutely hate to lose the guaranteed
synchronisation we get from using the same source. The best I could
come up with was keeping the XML format we have, and using XSLT in a a
pre-goal to morph it into what Maven likes. However, if what you've
got works already, that would be excellent!
We could consider using taglibdoc instead of our homegrown process.
With taglibdoc, the TLD files themselves become the primary source,
and the doc is generated, instead of vice-versa. There is a Maven
plugin for this.
Given how many attributes have accreted around our different HTML
tags, I kind of prefer the frameset/javadoc style of taglibdoc. I
played around with generating the doc from our own generated TLDs a
while back, and I was reasonably satisfied. Looks like I still have
the (possibly out of date) doc here:
http://people.apache.org/~germuska/struts-taglib/docs/tlddoc/index.html
If we plugged this in, it would appear under the project reports, as
you can see here:
http://people.apache.org/~germuska/struts-taglib/docs/maven-reports.html
I just noticed that in Wendy's generated docs at svn.apache.org, all
the "projects" come far below the "subprojects" in the navigation;
that might not be the clearest...
Joe
--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction" -The Ex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
