Usually, the wrapper creation used to work across a wide range of Gradle versions. Then, once the required Gradle version is installed, we indeed use that specific version. But I was expecting that I could at least generate the wrapper as usual, regardless of the version of Gradle I had locally (as long as it's not a too outdated one of course)
And by the way, the README does indeed say that this should work if you have a Gradle version close enough. On Tue, Oct 22, 2019 at 12:20 PM Cédric Champeau <cedric.champ...@gmail.com> wrote: > As the README says, you need to use the Gradle version which is declared > in gradle.properties, which is 5.6.3 for this release. > > Le mar. 22 oct. 2019 à 11:51, Guillaume Laforge <glafo...@gmail.com> a > écrit : > >> QQ, it's perhaps just a Gradle issue, but with the local version of >> Gradle I have (Gradle 5.3.1), I can't create the wrapper and I get: >> >> ↳ gradle -b wrapper.gradle wrapper >> >> >> FAILURE: Build failed with an exception. >> >> >> * Where: >> >> Settings file >> '/Users/glaforge/Downloads/groovy-3.0.0-rc-1/settings.gradle' line: 60 >> >> >> * What went wrong: >> >> A problem occurred evaluating settings 'groovy'. >> >> > There is no feature named GROOVY_COMPILATION_AVOIDANCE >> >> On Tue, Oct 22, 2019 at 11:19 AM Paul King <pa...@asert.com.au> wrote: >> >>> Dear development community, >>> >>> I am happy to start the VOTE thread for a Groovy 3.0.0-rc-1 release! >>> >>> This release includes over 50 bug fixes/improvements as outlined in the >>> changelog: >>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12345982 >>> >>> Groovy 3 is nearing lockdown status for final release. >>> One part which has only recently been finished and still needs a bit >>> more polishing is a revamped groovydoc. It no longer requires antlr2. >>> Groovy files are parsed using antlr4 and Java using >>> com.github.javaparser. Because this new version is less stable than the >>> rest of the release it currently is disabled by default and enabled with >>> the 'preview.groovydoc.antlr4' system property. The plan is for this >>> property to be removed before final release but feedback on existing >>> functionality welcome. You might need to include additional dependent jars >>> on your classpath when using the current version. >>> >>> Tag: >>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_0_RC_1 >>> Tag commit id: 2ede5187ca8e6adf0986d8284009abfd48876998 >>> >>> The artifacts to be voted on are located as follows (r36439). >>> Source release: >>> https://dist.apache.org/repos/dist/dev/groovy/3.0.0-rc-1/sources >>> Convenience binaries: >>> https://dist.apache.org/repos/dist/dev/groovy/3.0.0-rc-1/distribution >>> >>> Release artifacts are signed with a key from the following file: >>> https://dist.apache.org/repos/dist/dev/groovy/KEYS >>> >>> Please vote on releasing this package as Apache Groovy 3.0.0-rc-1. >>> >>> Reminder on ASF release approval requirements for PMC members: >>> http://www.apache.org/legal/release-policy.html#release-approval >>> Hints on validating checksums/signatures (but replace md5sum with >>> sha256sum): >>> https://www.apache.org/info/verification.html >>> >>> 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 3.0.0-rc-1 >>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >>> [ ] -1 Do not release Apache Groovy 3.0.0-rc-1 because... >>> >>> Here is my vote: >>> >>> +1 (binding) >>> >>> >> >> -- >> Guillaume Laforge >> Apache Groovy committer >> Developer Advocate @ Google Cloud Platform >> >> Blog: http://glaforge.appspot.com/ >> Twitter: @glaforge <http://twitter.com/glaforge> >> > -- Guillaume Laforge Apache Groovy committer Developer Advocate @ Google Cloud Platform Blog: http://glaforge.appspot.com/ Twitter: @glaforge <http://twitter.com/glaforge>
