Normally I would agree, but if a public class extends a "private" one then it should be visible. We have some Abstract* classes that have no Javadoc generated for them yet their subclasses are visible. This seems quite incorrect to me. Feel free to hide private APIs so long as no public ones expose them.

Gili

Martijn Dashorst wrote:
ah...

the good old argument between showing public API or all internal guts.

There have been several requests for providing more API docs, and none for providing just the public/protected API docs, so just commit it and we won't have this argument again (until someone complains that we provide too much API docs ;-).

Martijn


On 10/7/05, *Gwyn Evans* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    No, Martijn, in *this* case, I rather suspect it's back to the
    JavaDocs not being built with package level enabled, thus we see
    things like this...
    
http://wicket.sourceforge.net/apidocs/wicket/markup/html/form/DropDownChoice.html

      If you recall, there was a bit of a discussion on the dev list, but
    I'm not sure if there was a real resolution or it just tailed off.
    Anyway, the change required is to add the following to the bottom of
    the maven project.properties, which I've done locally but didn't want
    to commit the change unless it was agreed.

    # -------------------------------------------------------------------
    # J A V A D O C  P R O P E R T I E S
    # -------------------------------------------------------------------
    maven.javadoc.package=true

    /Gwyn

    On 07/10/05, Martijn Dashorst < [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:
     > You are (as all users) invited to submit patches, RFE's, bugs, wiki
     > articles, etc.
     >
     >  Patches are usually taken care of with higher priority than mere
    bug
     > reports. Be specific on what is missing:
     >  only 'javadoc is missing' will not trigger much response. On the
    other hand
     > 'Javadoc for x.y.z is incorrect here is a patch/better
    explanation' might
     > cause more interest.
     >
     >  When I look at the Wicket API documentation, I think it is
    pretty solid. It
     > is certainly a lot better than most open source projects out
    there. And we
     > know we don't have a reference manual, but we are (not
    constantly) working
     > on one.
     >
     >  Martijn
     >
     >
     >
     > On 10/5/05, Andrew Berman <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:
     > > I just downloaded it.  Any reason why some abstract
     > > classes in the doc are not built (e.g.
     > > AbstractTextComponent)?  I just rebuilt the docs so I
     > > could get everything to link up again.
     > >
     > > Also, I am a newbie to Wicket, but so far I love it.
     > > I am using it to build an application for my company.
     > > Consequently, I'd like to see it become more
     > > mainstream like Spring and Hibernate.  I think the
     > > reason those two projects are so incredibly successful
     > > is their documentation.  Their APIs are very well
     > > documented and their user guides are huge.  While I
     > > don't expect this to happen overnight, are there any
     > > plans for a release that would just beef up the docs,
     > > especially the API docs?  I'd love to help as I become
     > > more familiar with Wicket.
     > >
     > > --Andrew
     > >
     > > --- Martijn Dashorst < [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>>
     > > wrote:
     > >
     > > > The wicket team is pleased to announce the Wicket
     > > > 1.1-rc2 release!
     > > >
     > > > http://wicket.sourceforge.net
     > > >
     > > > Wicket is a Java web application framework that
     > > > takes simplicity, separation
     > > >
     > > > of concerns and ease of development to a whole new
     > > > level. Wicket pages can
     > > > be
     > > > mocked up, previewed and later revised using
     > > > standard WYSIWYG HTML design
     > > > tools. Dynamic content processing and form handling
     > > > is all handled in Java
     > > > code using a first-class component model backed by
     > > > POJO data beans that can
     > > > easily be persisted using your favourite technology.
     > > >
     > > > Changes in this version include:
     > > >
     > > >  New Features:
     > > >
     > > >    - added class
     > > > wicket.markup.html.image.resource.BlobImageResource
     > > > to
     > > >    make working with images from databases easier.
     > > >    - Made FileResourceStream non-final to support
     > > > using custom content
     > > >    type schemas etc
     > > >
     > > >  Fixed bugs:
     > > >
     > > >    - Image components inside a border component are
     > > > resolved by the
     > > >    parent of the border, thus keeping
     > > > pre-viewability and componentization.
     > > >    Issue: 1312787. Thanks to Ari Suutari.
     > > >    - Borders now treat autolinked resources within
     > > > wicket:head tags
     > > >    correctly Issue: 1289768. Thanks to Jan Bares.
     > > >    - skip content of script tag. Treat it as raw
     > > > markup Issue: 1287640.
     > > >    Thanks to Jan Bares.
     > > >    - Wrong impl. on getParameters() of
     > > > WebRequestWithCryptedUrl Issue:
     > > >    1275726.
     > > >    - Added serialversionuid to all the serialized
     > > > wicket classes Issue:
     > > >    1288373.
     > > >    - Link altered child visibility based on wicket
     > > > id; hidden 'feature'
     > > >    is removed now. Issue: 1297446. Thanks to Sven
     > > > Meier.
     > > >    - Improved hangman letter images to use just one
     > > > image reference.
     > > >    Issue: 1297449. Thanks to Sven Meier.
     > > >    - doc fix for Button.setDefaultFormProcessing
     > > > Issue: 1287878. Thanks
     > > >    to Leo West.
     > > >    - Call invalidate after each setXXX invocation on
     > > >    DefaultButtonImageResource to force re-rendering
     > > > Issue: 1266998. Thanks to
     > > >    Johan Compagner.
     > > >    - Made WicketExampleHeader.html (X)HTML compliant
     > > > Issue: 1267147.
     > > >    Thanks to Jan Bares.
     > > >    - Link.autoEnable is now false by default, and
     > > > when setEnabled is
     > > >    called, autoEnable will be set to false too as
     > > > calling setEnabled is a
     > > >    consious action that has no effect when
     > > > autoEnable is true Issue: 1251658.
     > > >    Thanks to Zhenbang Wei, Niclas Hedhman.
     > > >    - Link.autoEnable is now false by default, and
     > > > when setEnabled is
     > > >    called, autoEnable will be set to false too as
     > > > calling setEnabled is a
     > > >    consious action that has no effect when
     > > > autoEnable is true. Autolinks are
     > > >    autoEnabled by default, and so are the paging
     > > > navigator links. CHECK YOUR
     > > >    CODE WHETHER THIS HAS CONSEQUENCES FOR YOU!
     > > > Issue: 1240768. Thanks to Gili
     > > >    Tzabari.
     > > >    - Models not detached when checkAccess() returns
     > > > false. Issue:
     > > >    1290352. Thanks to Phil Kulak.
     > > >    - DatePicker fails when used multiple times in
     > > > the same page Issue:
     > > >    1290843. Thanks to Ralf Ebert.
     > > >    - Buttons with empty value are not found as
     > > > submit button Issue:
     > > >    1298789.
     > > >    - Persisted form values not loaded for
     > > > bookmarkable/redirect pages
     > > >    Issue: 1298795.
     > > >    - Moved Dojo and Scriptaculous dependencies out
     > > > of core into contrib
     > > >    packages Issue: 1298082.
     > > >    - Renamed pageableListViewNavigation field and
     > > > getter in
     > > >    PagingNavigator Issue: 1288863. Thanks to Igor
     > > > Vaynberg.
     > > >    - Patch for error in javadoc in ApplicationPages
     > > > Issue: 1294381.
     > > >    Thanks to Igor Vaynberg.
     > > >    - form now checks on enctype attribute. If the
     > > > attribute is multipart,
     > > >    the multipart property of the form object will be
     > > > set to that.
     > > >    - AJAX component doesn't get correct request
     > > > parameter path Issue:
     > > >    1292416.
     > > >
     > > >  Changes:
     > > >
     > > >    - Add WebPage(PageParameters) constructor (helps
     > > > with your IDE's code
     > > >    completion features) Issue: 1284625. Thanks to
     > > > Gwyn Evans.
     > > >    - made Link.isEnabled non final so that users can
     > > > more easily
     > > >    customize on/off behaviour.
     > > >
     > > >
     > > > Have fun!
     > > > -The wicket team
     > > >


    -------------------------------------------------------
    This SF.Net email is sponsored by:
    Power Architecture Resource Center: Free content, downloads,
    discussions,
    and more. http://solutions.newsforge.com/ibmarch.tmpl
    _______________________________________________
    Wicket-user mailing list
    [email protected]
    <mailto:[email protected]>
    https://lists.sourceforge.net/lists/listinfo/wicket-user



--
http://www.desktopbeautifier.com/


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to