eriwen
(Eric Wendelin)
February 13, 2017, 3:20pm
1
Gradle 3.4-rc-3 is now available for testing
This release candidate contains a few bug fixes reported against 3.4 RC2 .
#1347 : Compile classpath snapshotting and annotation processor detection should handle irrelevant files
#1351 : Add “unresolvable configurations” to the breaking changes section of the release notes of 3.4
#1358 : Compile classpath snapshotting should be lenient with broken jars/class files
#1359 : Lenient compile classpath snapshotting
#1371 : Gradle 3.4-rc-1+ handling of transative dependencies is non-passiveive
Check the 3.4-rc-3 release notes for more information. If no regressions are reported, a final release will typically follow in the next week.
Upgrade Instructions
Switch your build to use Gradle 3.4-rc-3 quickly by updating your wrapper properties:
./gradlew wrapper --gradle-version=3.4-rc-3
Standalone downloads are available at https://gradle.org/release-candidate .
Reporting Problems
If you find a problem with 3.4-rc-3, please file a bug on GitHub Issues adhering to our issue guidelines. If you’re not sure you’re encountering a bug, please use the forum .
eriwen
(Eric Wendelin)
February 13, 2017, 3:25pm
2
This topic is now a banner. It will appear at the top of every page until it is dismissed by the user.
There’s an issue with the release notes Markdown:
On https://docs.gradle.org/3.4-rc-3/release-notes.html#external-contributions , the last entry probably should not show up.
idlsoft
(idlsoft)
February 13, 2017, 3:49pm
4
Any chance for https://github.com/gradle/gradle/pull/1389 to be merged before the official release?
eriwen
(Eric Wendelin)
February 13, 2017, 4:19pm
5
@jochenberger Good catch, thank you. We’ll get that fixed.
eriwen
(Eric Wendelin)
February 13, 2017, 4:23pm
6
@idlsoft Not for 3.4. It looks like it’ll be included in the next version of Gradle.
idlsoft
(idlsoft)
February 13, 2017, 4:41pm
7
It’s a pretty significant issue - any code that executes outside the regular test boundaries that tries a simple System.out.println
will throw an exception.
Instances like this may be limited but, the very fact that gradle introduces side-effects into testing is troubling.
I’d also argue for a 3.3.1 hotfix.
bmuschko
(Benjamin Muschko)
February 20, 2017, 4:11pm
8
This topic is no longer a banner. It will no longer appear at the top of every page.