I just reverted the SDKMAN hack I described earlier (now `/usr/libexec/java_home` no longer works) and then proceeded to install NetBeans 19 (Apache-NetBeans-19.pkg, not the community installer) without any issue. So on my machine at least, it seems the hack is no longer required. Thank you, Neil, for letting us know the installer has been changed (fixed, from my perspective). Much appreciated!
Thanks, Phil p.s. I'd say whatever is listed first on the download page should "just work" so if we want to nudge people toward the community installers, I'd suggest moving them up. Or maybe there could be a note indicating that if the official installers don't work, please try the community installers. Personally, I'm happy to use the official installer. On Wed, Aug 30, 2023 at 5:19 AM Neil C Smith <neilcsm...@apache.org> wrote: > On Wed, 30 Aug 2023 at 02:11, Philip Durbin <philipdur...@gmail.com> > wrote: > > I had the same problem. I'm using SDKMAN and could not install NetBeans > 18 on my Mac because the NetBeans installer said "No Java found". > > > > I fixed it by following > https://stackoverflow.com/questions/76523553/how-to-make-usr-libexec-java-home-find-jdk-installed-using-sdkman-on-macos > > Thanks! Note that NetBeans 19 will have a completely different > installer. This will rely on the launcher finding a JDK. It will be > interesting to see whether that requires the same fix. > > Unless there is a particular need to run the IDE on a specific JDK, I > would recommend using the community installer for macOS that includes > a local JDK for the IDE to run on. Then everything is signed together > in a single bundle. You can still use SDKMAN JDKs for any projects. > > Best wishes, > > Neil >
