+1 for hiding. If the internal classes were shaded from another artifact they wouldn't appear in the Javadoc, so let's be consistent and hide anything not meant for public usage.
Emmanuel Bourg Le 12/01/2014 14:34, sebb a écrit : > On 12 January 2014 10:18, Stefan Bodewig <bode...@apache.org> wrote: > > I think it's better to keep the Javadoc, and be explicit about not > using it, rather than hoping people won't use classes that don't > happen to have Javadoc. > It's not possible for a user to tell if the Javadoc is deliberately or > accidentally missing [1]. > > In fact I would go a bit further and change the class Javadoc: > > Base-class for traditional Unix ".Z" compression and the Unshrinking > method of ZIP archive. > > to add something like "Internal use only. May change or disappear > without warning.". > > > [1] Remember the manual pages which stated "This page is intentionally > left blank"? Similar reasoning here. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
