The "migration" may not be painful but breaking user builds or plugins when they upgrade Gradle is not cool. Several issues have been filed already as I understand.
Le sam. 13 oct. 2018 à 17:41, Daniel.Sun <sun...@apache.org> a écrit : > Hi Cédric, > > > However, we discovered several regressions (in @CompileStatic, in > > covariant return type checking, ...) that may make the migration > painful. > According to the changed files shown in the PR ( > https://github.com/gradle/gradle/pull/6903/files ), it seems that the > migration is not that painful ;-) > > BTW, all changes for 2.5.x pass all existing tests in Groovy project. > If you find some breaking change, feel free to submit JIRA ticket to track. > > Cheers, > Daniel.Sun > > > > > ----- > Daniel Sun > Apache Groovy committer > Blog: http://blog.sunlan.me > Twitter: @daniel_sun > > -- > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html >
