Just an item of feedback, and I guess a minor irritation. Between Gradle (which tends to have multiple copies of each and every jar it needs), Ivy (which has lots of jars as well), Maven (which tends to download the entire universe of jars at any possible opportunity), and Grapes which stores jars separately again from anything to do with Gradle, Ivy, or Maven, I am ending up with large numbers of copies of the same jars. Whilst disc is cheap this really is just profligate.
Given that Gradle and Grapes use Ivy, I don't see why there has to be so
many copies of the jars, why not just one in the Maven repository and
one in the Ivy repository?
I can see why there might need to be separate metadata, that's not the
point at issue, the point is that there should only be one copy of the
jar for each transport mechanism, not each application.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
