On 2014-01-12, Stefan Bodewig wrote:
I'm a bit torn on this and since I'll re-roll a new RC anyway I'd like
to see what others think about hiding internal packages.
I've unhid it again and strengthened the may change warning as Sebb
suggested. Making things explicit feels better to me.
Compress holds a package that is public as an implementation detail but
whose API isn't meant for public consumption. The javadocs of said
package state this in bold letters.[1]
Current trunk will even go further and hide the package from javadoc,
but the only class inside is still refered to by
On 12 January 2014 10:18, Stefan Bodewig bode...@apache.org wrote:
Compress holds a package that is public as an implementation detail but
whose API isn't meant for public consumption. The javadocs of said
package state this in bold letters.[1]
Current trunk will even go further and hide the
:18 (GMT-05:00)
To: dev@commons.apache.org
Subject: [compress] exclude _internal package from javadocs?
Compress holds a package that is public as an implementation detail but
whose API isn't meant for public consumption. The javadocs of said
package state this in bold letters.[1]
Current trunk
+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
