-
Notifications
You must be signed in to change notification settings - Fork 853
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
Upgrade Gradle Tooling API to 8.10 #7690
Conversation
mbien
commented
Aug 22, 2024
- full JDK 23 support
- https://docs.gradle.org/8.10/release-notes.html
Hi @mbien. I was wondering if this PR is ready for review or do you expect more changes? Would this be planned for NB23 delivery? Thanks. |
@sid-srini this PR wasn't picked up for NB 23 so it is likely going to end up in NB 24 or closed. I posted two mails to the dev list when I opened the maven/gradle PRs: the way I understand this is that the gradle tooling upgrade is not technically needed since the gradle project init script is already using "newest", which should init with the latest available wrapper. However I never could get this to work (it always picked 8.9), others reported that it does work though. |
Thanks @mbien for the delivery references.
Thank you. |
yep. but in theory this should already happen with NB 22. (it didn't work for me either, but others claimed that it does work) netbeans/extide/gradle/src/org/netbeans/modules/gradle/spi/newproject/GradleInitWizard.java Line 210 in c934998
it tells gradle to use the latest available wrapper edit: if you test this, make sure you clean your ~/.gradle folder which caches a lot of things |
- full JDK 23 support
due to popular demand I rebased this on top of delivery in case there is spare capacity to review this for NB 23 - if not I can move it back to master/NB24 - no problem. PR produces a dev build for convenient testing. |
@sid-srini has any testing been done with the patch outside quick checks if new-project init works on JDK 23? |
Yes, I have checked the following with NB running on both JDK 22 and 23:
This did not work for me either. I got the following results for the gradle versioned link that is stored in the wrapper on init:
|
Backport NB patch apache/netbeans#7690 for Gradle tooling 8.10 upgrade
LGTM |
@sid-srini thanks a lot for the info! It helps to know what has been tested in such last-minute PRs. |
sdedic is on vacation this afternoon. Seeing he did not objected and was on PR for a while I think it is OK to merge to NB23. So merge it |
One (small?) problem with this update is that the wizard now defaults to JDK 23, which then takes a while downloading a JDK via Disco without much feedback. Probably not a showstopper for NB24, and mainly the behaviour that was already there, but the wizard should probably default to the running JDK if possible in NB24? |
I think what it could do is to indicate if it will dl a JDK or not. User can decide what to do. The default of Java 23 (essentially latest known) is probably fine for NB 23 since it overlaps with JDK 23 GA but I wouldn't mind setting it to the NB runtime JDK. (also note that the draft of the NB download page does also mention JDK 23 as supported runtime JDK apache/netbeans-antora-site#29) I vaguely remember pointing out that gradle simply downloading stuff without asking is probably not ideal on the PR which implemented this. |