On 12/10/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I'm thinking about a custom JavaDoc doclet to generate component documentation, since most of what you need to document is private. Alternately, perhaps Tapestry code JavaDoc should just include privates as well as everything else?
I would go with the inclusion of privates methods within JavaDoc, that would reveal how public/protected methods would like to act. -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
