commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject [POOL] documenting the public API
Date Fri, 04 May 2012 15:14:41 GMT
I think it would be useful to try and specify upfront which public
classes / methods etc are intended to form part of the public API, to
distinguish them from items that are public merely to allow internal
access between packages.

If changes are later needed to public classes that are documented as
not being part of the public API, we can potentially break binary
compatibility if necessary.

Maybe consider using a separate package name element such as "internal" ?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message