-
Notifications
You must be signed in to change notification settings - Fork 38.5k
Upgrade to Gradle 4.8(.1) [SPR-16475] #21020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Juergen Hoeller commented A line from our
|
Sam Brannen commented FYI: Gradle 4.6 was released just a few hours ago... |
Sam Brannen commented Related to #21213 |
Sam Brannen commented Merged PR into |
Juergen Hoeller commented Reopening for a Gradle 4.7 upgrade... reusing this issue since we haven't released against it yet. |
Sam Brannen commented Upgraded to Gradle 4.7 in commit: 5811d13 Upgrade to Gradle 4.8 in commit: 2390695 |
Juergen Hoeller commented Sam Brannen, thanks for your efforts there! Since master is on Gradle 4.8 now, including all of Gradle's JDK 10 related changes already, I consider this good enough for our Spring Framework 5.1 RC1 in July... just possibly upgrading to Gradle 4.8.1 (if any) in the course of this ticket still. Let's use a separate ticket for any further major Gradle upgrades, individually scheduled for 5.1.x or 5.2. |
Sam Brannen commented Sounds like a good plan! |
Juergen Hoeller commented I've updated the build to Gradle 4.8.1 now. |
Sam Brannen commented I'm guessing you mean locally, but... OK. ;-) |
Juergen Hoeller opened SPR-16475 and commented
Gradle 4.5 is out in the meantime, with even a 4.5.1 maintenance release available already... and now Gradle 4.6 goes RC, so we should go straight to that one.
Update: Gradle 4.7 is out now. Maybe we'll even get Gradle 4.8 in time for our 5.1 RC1...
Affects: 5.0.3
Issue Links:
Referenced from: commits 17c16ea, 853d30d, eaffcbe
The text was updated successfully, but these errors were encountered: