commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: [POOL] documenting the public API
Date Sat, 05 May 2012 20:35:22 GMT
On 04/05/2012 17:14, Mark Thomas wrote:
> sebb <> wrote:
>> 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.
> I'd prefer to move things between packages and make them package
> private if at all possible. I should be able to take a look at that
> over the next few days. I have an OS license of Structure 101 and
> I'll run that over it as well along with PMD and friends.

Short version of Structure 101 analysis is that there is nothing to
worry about. No nasty circular dependencies (apart from in the unit
tests and I don't mind them there).


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

View raw message