Those classes are declared as 'package' rather than 'public' and by default, JavaDoc's only generated for public & protected elements. We had a bit of a discussion, though, and changed the project properties such that they too should have generated docs from the next release.
/Gwyn On 07/09/05, Scott Sauyet <[EMAIL PROTECTED]> wrote: > It seems quite odd to me that a few of Wicket's classes don't show up in > the Javadoc. I haven't done any investigating into why; I don't really > even know how to go about that. But if anyone has some ideas, it would > be worth at least knowing the reason. > > The classes that I've noticed are all in wicket.markup.html.form: > > AbstractChoice > AbstractSingleSelectChoice > AbstractTextComponenet > > Any ideas? > > -- Scott > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
