On Wed, 9 Mar 2022 at 11:14, Michael Bien <[email protected]> wrote: > > These are built with NBPackage using the official ASF zip release, but > > are obviously third-party unofficial binaries themselves. > > pretty cool! Is the JDK installed globally or is it only used by NB?
With these it's only local as part of the overall package. Location within the package differs slightly depending on package type. It's the package.runtime property in NBPackage, which is optional, and could also be a custom (JLink'd) runtime, although more for RCP than the IDE. More info / build config at https://github.com/apache/netbeans-tools/tree/master/nbpackage https://github.com/codelerity/netbeans-installers In theory, something like the Inno Setup installer could also be templated to include a JDK installer and run that first. Would be good if the JDK location detection in the launcher still worked on Windows. Am looking at a way to add it into the Inno Setup installer and shortcut instead. If we can get useful JDK detection to work there, it might also be possible to publish a JDK-less Windows installer built that way as an ASF artefact. The .deb without JDK already could be. > > Feedback appreciated. And how would we feel about linking to > > third-party convenience binaries from the Apache NetBeans website? > > sure why not. Maybe in a community-packages section or something like that? Yes, or third-party packages? I would suggest adding wording similar to httpd? - "Individual committers may provide binary packages as a convenience, but it is not a release deliverable.", although with the latter part rewritten somewhat so it's more understandable by humans! :-) Best wishes, Neil --------------------------------------------------------------------- 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
