Dion Gillard wrote:
The idea with the tag reference was to have a one stop place for all the documentation.
I thought this was what libs/index.html does. It's generated before xdoc:transform
So the correct way for working would be to enrich libs/index.html with a link to examples... right? Anything else than unit-tests ??If we can do that with links and by improving the individual taglib documentation, I'm all for it.
What's that wrong ?? If the javadoc comments are inadequate, we need to make them correct, I think the jellydoc takes precedence of javadoc... or ?The problem with the current taglib documentation is that a) it's autogenerated off inadequate source markup
b) It doesn't provide examples and usage info.
how would you document examples except with unit-tests ??
paul
On 7/25/06, Paul Libbrecht <[EMAIL PROTECTED]> wrote:It isn't easy as that, building the site does take a huge time because of the very many tag-libs.... depending on the maven version this may even turn out to impossible. This tag-reference page makes double usage with: http://jakarta.apache.org/commons/jelly/libs/index.html whose links are all correct... why keep it ? Rebuilding the site would probably fix it if replacing tag-reference/x.html with libs/x/tags.html but do we really need that ?? paul Dennis Lundberg wrote: > That might be so, but the links on the "All tags" page work. So it's > just a matter of fixing some links. If I go ahead and do that would it > be OK to redeploy the site? > > Dion Gillard wrote: >> I don't think the tag reference is complete. >> >> On 7/25/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: >>> Hi >>>>>> The links under "Tag Reference" are all broken. That is all except "All>>> tags". >>> http://jakarta.apache.org/commons/jelly/tag-reference/index.html >>>
smime.p7s
Description: S/MIME Cryptographic Signature
