No problem, djKianoosh. I didn't find a link to it from the main gradle doc. The javadoc lays it out:
"Adds a repository which looks in the local Maven cache for dependencies." http://gradle.org/current/docs/groovydoc/org/gradle/api/artifacts/dsl/RepositoryHandler.html#mavenLocal%28%29 So, the mavenLocal repository is definitely distinct from the gradle cache*. Cheers, Merlyn * You can take a look at the internal Gradle class, MavenSettingsProvider too if you like. On Thu, Jul 7, 2011 at 9:01 AM, djKianoosh <[email protected]> wrote: > Not to hijack this thread ;-) but could you explain this a bit more please? > (or maybe start a new post about this). I haven't had any issues using > mavenLocal() up to now so I'm very curious... > > > M A wrote: >> >> I'd avoid using mavenLocal, as I understand it that looks at your >> ~/.m2/repository directory and is therefore a source of build portability >> bugs. >> > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Issue-with-webAppDirName-and-war-plugin-tp4560665p4561534.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 > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
