$ gradle wrapper
FAILURE: Build failed with an exception.
Build file '/Users/glaforge/Downloads/groovy-2.6.0-alpha-2/build.gradle' line: 53
* What went wrong:
An exception occurred applying plugin request [id: 'com.gradle.build-scan', version: '1.6']
> Failed to apply plugin [id 'com.gradle.build-scan']
> This version of Gradle requires version 1.8.0 of the build scan plugin or later.
Please see https://gradle.com/scans/help/gradle-incompatible-plugin-version for more information.
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
* Get more help at https://help.gradle.org
Which might also be why Cédric committed a change related to the build scan plugin?
On Sat, Nov 11, 2017 at 4:24 PM, Daniel.Sun <firstname.lastname@example.org> wrote:
> Dear community,
> I am happy to start the VOTE thread for a Groovy 2.6.0-alpha-2 release!
> This release includes 10 bug fixes/improvements as outlined in the
jira/secure/ReleaseNote.jspa? projectId=12318123&version= 12341386
org/repos/asf?p=groovy.git;a= tag;h=refs/tags/GROOVY_2_6_0_ ALPHA_2
> Tag commit id: 3c37e8ce66613901f1b523b0519fb6
> The artifacts to be voted on are located as follows (r23058).
> Source release:
> Convenience binaries:
> Release artifacts are signed with a key from the following file:
> Please vote on releasing this package as Apache Groovy 2.6.0-alpha-2.
> The vote is open for the next 72 hours and passes if a majority of at least
> three +1 PMC votes are cast.
> [ ] +1 Release Apache Groovy 2.6.0-alpha-2
> [ ] 0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.6.0-alpha-2 because...
> Here is my vote:
> +1 (binding)
> Sent from: http://groovy.329449.n5.