Gradle 3.2-rc-3 is now available for testing

Gradle 3.2 RC3 is now available for testing

This release candidate contains a few bug fixes reported against 3.2 RC2.

  • GRADLE-3579: Generated scripts in Gradle 3.2 spawn child processes
  • GRADLE-3580: IntelliJ Gradle import does not resolve sources for dependencies
  • GRADLE-3581: Build fails for Kotlin project with multi-level project dependencies

Check the 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.2 RC3 quickly by updating your wrapper properties:

./gradlew wrapper --gradle-version=3.2-rc-3

Standalone downloads are available at

Reporting Problems

If you find a problem with Gradle 3.2 RC3, 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.

Known Issues

This topic is now a banner. It will appear at the top of every page until it is dismissed by the user.

Everything fine with the usual projects.

The only (small) issue I had was the following output while executing ./gradlew wrapper the second time:

[..]/gradlew: line 172: syntax error near unexpected token `&&'
[..]/gradlew: line 172: ` && [ "$HOME" = "$PWD" ]; then'

This happens when wrapper is executed a second time, i.e. using the freshly downloaded new Gradle version. I always execute wrapper twice after changing the version in build.gradle so that the new Gradle version gets the chance to update script files. (Yes, I know that It don’t have to specify the version in the build script anymore. But I actually like it that way.)

Everything is working fine, though, and this probably only happened because I used previous RCs. Just a cosmetic issue.

Hi Jörn,

yes the failure occurs once if you installed one of the previous RCs before. But it is actually a good thing, because it means that a regression with the start script we had in rc1/rc2 is fixed. :slight_smile:

Thanks for reporting and let us know if you encounter anything else that looks suspicious.

1 Like

This topic is no longer a banner. It will no longer appear at the top of every page.