On 8/20/06, Ted Husted <[EMAIL PROTECTED]> wrote:
So, if we follow this tact, the action plan would look like:
* Update TLD from WW head and revise class references
** (/s/com.opensymphony.webwork/org.apache.struts2)
Since WW 2.2.3 just hit the street, I'll update our TLD to match the
one in that distribution, and proceed with the rest of the plan. I'm
thinking we could tag the build for 2.0.0 within the next few days. It
sounds like the new API is almost done, so we should have that ready
for 2.0.1.
I already updated the "Tag Developers Guide" to reflect the new taglib
references, and it's looking good!
* http://cwiki.apache.org/WW/tag-developers-guide.html
* Update TLD with snippets from Javadocs
** Remove example snippets from Javadocs (to avoid maintenance)
* Refer to Tag Reference (and Javadocs) from wiki docs
** Remove old tag reference pages
* When creating a distribution, update references in the wiki docs to
point to a local copy of the Tag and Java references. (ugh!)
* Work with maven-taglib team to fix "no-wrap example" and "ignores
enities" issues with tlddocs
(http://sourceforge.net/tracker/index.php?func=detail&aid=1543474&group_id=93991&atid=606303).
So, moving forward, we would maintain the struts-tags.tld, embedding
the example code there, and let the plugin generate the tag reference
and tag API docs. We would not need to maintain the xdoclet code, or
create a reference page in the wiki for each tag.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
