There were a number of changes in 1.9 surrounding mavenLocal and properly handling artifacts contained in it and publishing (installing) to it.
What kind of errors are you seeing? Dependency resolution errors? How are the artifacts in your mavenLocal getting into there? Where they published (installed) from a previous version of Gradle? The change you're making to work around the issue is setting up a normal Maven distribution repository at the same path as mavenLocal. While this works, this is actually the issue that was fixed in 1.9 because mavenLocal has different rules around its behavior then standard maven repository. -- View this message in context: http://gradle.1045684.n5.nabble.com/mavenLocal-regression-in-1-9-tp5712124p5712125.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
