I guess we should upgrade the version of the plugin anyway so that bootstrapping via Gradle 4 works. Using --no-scan doesn't even help in that case unless someone else knows a workaround.
Cheers, Paul. On Thu, Jun 22, 2017 at 4:46 PM, Paul King <pa...@asert.com.au> wrote: > > Are you using: > > gradle wrapper > gradlew dist > > As per README.adoc? The 'gradle wrapper' step should work bootstrapped > with 3.5 but otherwise each Groovy distribution declares what Gradle > version it is designed to build with as per the wrapper setup. > > Cheers, Paul. > > > On Thu, Jun 22, 2017 at 3:59 PM, Balachandran Sivakumar < > balachand...@balachandran.org> wrote: > >> Hi, >> >> >> The artifacts to be voted on are located as follows (r20140). >>>> Source release: >>>> https://dist.apache.org/repos/dist/dev/groovy/2.4.12/sources >>>> >>> >> When I try to build this from the source zip, I get the following >> build failure with Gradle 3.5 >> >> :groovydocAll FAILED >> >> FAILURE: Build failed with an exception. >> >> * What went wrong: >> Execution failed for task ':groovydocAll'. >> >>> java.lang.ExceptionInInitializerError (no error message) >>> >> >> >> Build Scan: https://scans.gradle.com/s/xobecl5cdgzhg >> >> Also, on Gradle 4.0, the build fails due to build-scan plugin >> incompatibility >> >> FAILURE: Build failed with an exception. >> >> * Where: >> Build file '/tmp/groovy-src/groovy-2.4.12/build.gradle' line: 48 >> >> * What went wrong: >> A problem occurred evaluating root project 'groovy'. >> >>> Failed to apply plugin [id 'com.gradle.build-scan'] >>> >> > This version of Gradle requires version 1.7.4 of the build scan >> plugin or later. >> Please see https://gradle.com/scans/help/ >> gradle-incompatible-plugin-version for more information. >> >> >> Am I missing something or doing something wrong ? Thanks >> >> >> -- >> Thank you, >> Balachandran Sivakumar >> > >
