On Sun, 2008-10-05 at 02:28 -0700, Peter Niederwieser wrote: > Doesn't Gradle maintain its own cache for build dependencies? I'm not sure > whether Gradle should use Maven's local repository. To do this Gradle would > have to know about a Maven installation, parse its settings.xml (to find the > repository), understand repository metadata, etc. Also local Maven > repositories must not be used concurrently, and their metadata gets > corrupted every now and then. I have spent a lot of time with Maven, and my > general advice is: avoid it if you can.
The problem here is though that if the Maven repository is being used then it should be used as the user believes the Maven repository behaves. So if the method was called: searchTheStandardMavenRepositoriesForDependenciesAndCacheThermInTheGradleCache then you would expect some behaviour that is not Maven standard. However the method is called: addMavenRepo so there is some expectation that the behaviour will be that of Maven when it comes to looking up dependencies. I guess I can live with manually adding the local Maven cache, but there really needs to be a platform independent label for it since it may not be at System.properties.'user.home'/.m2/repository on all systems. PS Of course Jason Dillon's advice will be "Use Maven whenever you can." :-) -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
