Russel Winder-4 wrote: > > 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 people's expectations are very different. I'd expect anything built on top of Maven (e.g. a Maven plugin) to follow Maven's dependency resolution mechanism, but I'd be very surprised if Gradle touched Maven's local repository (I wouldn't even recommend to share the local repo between two Maven installations). addMavenRepo() means "add the (remote) Maven repository http://maven1.repo.org";, and for my taste the method name communicates this fairly well. Maybe addOfficialMavenRepo() would be even clearer. Russel Winder-4 wrote: > > PS Of course Jason Dillon's advice will be "Use Maven whenever you > can." :-) > I wasn't really interested in GMaven until I realized that it would allow me to script Maven with Groovy! This has since saved my day a few times, but Maven sucks nevertheless. :-) Cheers, Peter -- View this message in context: http://www.nabble.com/Maven-repository----I-should-know-the-answer-but...-tp19820914p19828191.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
