The Gradle team is pleased to announce that the second release candidate for Gradle 2.2 is now available.
This second release candidate fixes three regressions reported in Gradle 2.2-rc-1:
incompatibility issues with the Jar task (GRADLE-3185)
incompatible changes in gradles configuration resolution process
Download links and release notes with further information can be found as always at http://gradle.org/release-candidate. Please try Gradle 2.2-rc-2 with your projects and let us know your experiences.
Attempting to change configuration ‘:horizon:compile’ after it has been included in dependency resolution. This behaviour has been deprecated and is scheduled to be removed in Gradle 3.0 Attempting to change configuration ‘:horizon:runtime’ after it has been included in dependency resolution. This behaviour has been deprecated and is scheduled to be removed in Gradle 3.0
Hey Christian, no this will not be fixed in 2.2. Once a release candidate is released we don’t do any changes/fixes for that version apart from regression fixes.
I’m seeing lots of messages like the following when I do a clean build:
Compilation failed for [SourceFile[/Users/jbisotti/sandbox/.../src/test/groovy/com/.../FooSpec.groovy]].
I haven’t check too closely, but it looks like one of these lines for each Groovy (Spock) spec. However, the build is successful and the tests seem to be run.
Update (5 Nov): I just checked and the same thing happened with RC1 as well.
I was using Gradle 2.1 in conjunction with grails-gradle-plugin 2.1.1 and it worked. Due to GRADLE-2871 I switched to 2.2-rc-2. Unfortunately this gives a
Will that class be permantenly removed (or package visible or whatever is the case here)? Then I will contact the author of https://github.com/grails/grails-gradle-plugin and ask for a compatible update.
It’s likely that the very old version of Groovy that CodeNarc uses has a problem with Spock’s compile transform. You can try adding a newer version of Groovy to the ‘codenarc’ dependency configuration.