Weakness of "requires public"

[Mark Derricutt]

On 27 Jul 2016, at 8:27, Malachi de Ælfweald wrote:

> I would not expect to specify any transitive dependency.  I would not
> expect any user of my API to have to manually specify any transitive
> dependencies I used in my public API (return types for example).  If they
> did - that completely breaks the point of me specifying transitive
> dependencies in the first place.

My view on this - if your code requires those dependencies to compile or be resolved by the class loader, it should be declared - otherwise its an internal dependency of that module and (could) be pulled in transitively to RUN/TEST.



-- 
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt