Bleeding Edge Gradle

(jim northrop) #1

I like to live life in the fast lane. I like my build tools to do the same. How about a fix so that the wrapper task always keeps my build on the bleeding edge ? So that avoids me needing to fix umteen build.gradle scripts when your magic fingers put out a new release ?

Maybe ‘current’ for the release you consider most stable ( 1.8 ) and latestRC for the bleeding edge like 1.9-rc-1

task wrapper(type: Wrapper) {
    gradleVersion : current


task wrapper(type: Wrapper) {
    gradleVersion : latestRC

(Luke Daley) #2


There’s nothing built in, but you can script up some stuff dynamically like we do to hit our version web service.