Jason T. Greene wrote:
Dependencies have significant impact on public projects. Every
dependency added is another possible version conflict with someone's
environment. You are also locked into whatever that dependency does, so
if you need to fix/customize something in the dep, you sometimes have to
patch and ship your own version. It also annoys users when a project
they uses sucks in N libraries, which each include N more, ad infinitum.
+1000
For my taste, Infinispan has way too many dependencies already !
So every dep needs to offer significant functionality to justify its
existence, and a few small collection classes don't really do that.
Exactly
Whereas depending on something like a network communication layer,
that
is over a hundred thousand lines of code makes sense.
Ha ha got you :-)
--
Bela Ban
Lead JGroups / Clustering Team
JBoss