Using the Maven repository appears to work fine in Gradle. Adding the addMavenRepo ( ) into the dependencies does what is needed. However, I am wondering if Gradle is using the right strategy regarding the local cache.
When I use Maven, it caches everything to a known place
($HOME/.m2/repository by default). Also when I do "mvn install" on a
project I get new material that is not in the Maven repository placed in
my local cache so that I can access it as though it were in the
repository without having to do anything special.
With Gradle I am finding that in order to access the material that is in
my local cache but not in the repository I have to explicitly name the
local cache:
addMavenRepo ( 'file:///home/users/russel/.m2/repository' )
This seems wrong to me, it means that the Maven repository search in
Gradle is not using the same lookup rules as Maven itself.
I am hoping someone can point out the really obvious thing I am doing
wrong :-)
Thanks.
--
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
