Hi all - I just saw this commit in the master branch which would put it on track from Gradle 1.12 - https://github.com/gradle/gradle/commit/97fb925848249251129f7ea0d70f12bdf112f2d0 <https://github.com/gradle/gradle/commit/97fb925848249251129f7ea0d70f12bdf112f2d0>
This introduces a breaking change (as noted in the release notes) regarding dependencies that have a 'pom' packing type. Basically, it forces Gradle to assume that a dependency also as an associated Jar regardless of the packing and if it doesn't it fails. I'm curious why this change is being made? I couldn't find a forum topic or recent JIRA ticket related to it. These was the behavior of Gradle <1.9 and prevented Gradle from being used on the same systems being used for Maven build (i.e. a CI server). This is because Maven installs a number of artifacts like this into the local .m2 cache. For every dependency it downloads the pom file into the local .m2 and then only downloads the Jar for the conflict resolved version. This leaves orphaned POM files in the .m2 and if a Gradle build comes along and wants that version, it would error because the Jar file isn't available. It seems this commit is simply re-instating the previous behavior which will again make Gradle builds fail on systems that are also building Maven projects (or even Grails projects using Aether since they utilizing the .m2 cache in the same manner). -- John Engelman -- View this message in context: http://gradle.1045684.n5.nabble.com/Breaking-change-for-POM-packaging-in-Gradle-1-12-builds-tp5712246.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
