On Wednesday, November 5, 2003, at 09:26 AM, __matthewHawthorne wrote:
I, for one, like the idea of commons projects depending on each other when necessary. There is always a lot of controversy with regards to "including another jar" that I don't quite understand. I agree that if there are only 1 or 2 references, it may be reasonable to include the dependencies as package private classes, or make more of an effort to avoid them in the first place. But this avoidance of code reuse sometimes disturbs me.
Are you short on disk space or something? To me, 850 kb isn't really that much.
Reuse where the price of reuse is lower than the price of a better design is fine, but here the better design cost is negligible. Don't add dependencies unless you really need them, please.
Why does a math module depend on a logging module for deployment? Have the unit tests log, not the math functions.
=)
-Brian
PGP.sig
Description: This is a digitally signed message part
