On Sat, 5 Nov 2022 at 07:26, Laszlo Kishalmi <[email protected]> wrote: > Well, yes I usually pull Gradle upgrade when it is likely to have a GA > during the RC phase. Unfortunately this is not the case now. > > Also I usually do not upgrade the bundled Gradle tooling libraries with > patch releases, if there is no fix in that area. The tooling shall be > back and forward compatible between Gradle versions to a certain limit. > > Reverting back to Java 17 or 18 as IDE runtime would be a solution. > Though it seems this time we reached too deep into the Gradle internals > an got burned. That means you've found a real bug. Would you report it > on github? We might be able to do an RC4 for NB-16. Though it is > possible that it would be NB-17.
This certainly sounds like it might be one to fix for 16, if doable. I didn't see the original email (below) you replied to?! I was planning a thread to discuss scheduling around Gradle post-release. Was happily testing NB16 on JDK 19 until I realised that Gradle didn't work - most of my projects are Maven-based. With JDK release, then Gradle release, it seems like it'll be NB17 before we can fully support running on (or for us, bundling with) JDK 19. Currently that's going to be just a couple of weeks before JDK 20. Is there anything we could change scheduling and/or tooling wise that might improve that? Best wishes, Neil > On 11/4/22 21:04, Scott Palmer wrote: > > I’ve been fiddling around with NB 16 rc-3 on my Mac where I had JDK 19 > > installed. I noticed that regardless of my project settings, NB is using > > Gradle 7.5 for tooling and can’t run on JDK 19 without getting class > > version errors related to running ‘cp_init'. > > > > While seeing if any settings could fix it, I noticed that the drop-down to > > choose a Gradle version shows 7.6-milestone-1 and some 8.0-milestones, but > > it doesn’t show a choice for 7.6-RC-1 (with JDK 19 support). Though it > > appears that wouldn’t address the issue anyway. > > > > I’m wondering if the embedded Gradle version should be bumped to 7.5.1 > > instead of 7.5 at least. I have doubts that Gradle 7.6 will be released > > before NB 16, but using it to get JDK 19 support for Gradle projects in NB > > would be great. > > > > When I edited netbeans.conf to force NB to run with JDK 17, my project that > > uses Gradle 7.6-rc-1 via the Gradle wrapper and JDK 19 (via Gradle Java > > Toolchain support) still claimed that it would not load. The only error > > message shown is: > > > > 'boolean > > org.gradle.api.internal.provider.ValueSupplier$ExecutionTimeVaue.isFixedValue()’ > > > > The message says priority Low, category Warning… but not loading the > > project seems like it should be a bigger deal. However... > > > > The funny thing is that the project does appear to load and build! Though > > when I build it there is a popup message: > > > > "Could not run build action using connection to Gradle installation > > ‘/Users/scott/dev/gradle’” that appears AFTER the build finishes without > > errors, > > > > I had the Gradle settings in NB set to use that fixed path for Gradle and > > ignore my wrapper settings. It is the path to my Gradle 7.6-RC-1 install, > > though I don’t need it to be 7.6 to run the Gradle script.. > > > > > > Regards, > > > > Scott > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
