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:
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.
Hi This release fixed my problem (http://forums.gradle.org/gradle/topics/gradle-2-2-rc-1-is-now-available-for-testing), my project can be built, but it raise the warning:
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
So what should I do to remove this warnning?
Any chance that GRADLE-3157 will be fixed ?
Right now, as soon as someone is using the “-parameters” option, all tests will fail.
This won’t be fixed for 2.2. We can work to get it fixed for 2.3.
That would be great!
Please see https://github.com/softappeal/GRADLE-3157_BugExhibit for a very small project showing the bug.
how about the following issue? https://issues.gradle.org/browse/GRADLE-3091
Will this come into Gradle 2.2?
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.
Hey Rene, thank you for your quick reply. any info, in which release this issue will be involved?
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
The full stack trace is provided at http://pastebin.com/HHJabnfi
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.
That change won’t be reverted, so the Grails plugin will have to be updated.
No other reports of this.
Looked into this a bit more. It seems to have something to do with Codenarc; that’s where the message is coming from:
6:14:42.541 [WARN] [org.codenarc.source.AbstractSourceCode] Compilation failed for [SourceFile[/Users/jbisotti/sandbox/.../src/test/groovy/com/.../FooSpec.groovy]].
./gradlew clean test
./gradlew clean codenarcTest
shows the compilation failure messages.
I’m running on OS X 10.9.5, with a Java 7 JDK, Gradle 2.2, Groovy 2.3.7, Codenarc 0.22.
It will be down to this change: http://gradle.org/docs/current/release-notes#codenarc-plugin-groovy-version-changes
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.
Looks like someone else reported the problem while I was idle: https://github.com/grails/grails-gradle-plugin/issues/128
I’ll get the grails plugin updated in the next couple days. Please refer to the link above for details.