1) would be great, as long as it works for the platform too, and would be a major benefit to the zip as well. You might not be the only person looking at launcher code right now, so some coordination of approach might be good.
Noted! I'll stay away from that piece of code for now, and follow the discussion on the mailing list. 2) is unnecessary - we can already build a Windows installer using NBPackage - the only thing stopping us switching a long time ago is something like 1). OK, very good. Is the thing it generates an InnoSetup EXE that does not by itself require Java? > Personally, I'm still in favour of dropping installers here, because of the > overhead Are you referring to the work added to the release process itself? Totally understand... and by the way, I'm extremely grateful for the recurring volunteer work you and others have done for that part of the project. > installers without a runtime have other issues Even if netbeans64.exe is updated to prompt for a JDK folder? > I remain of the view that if you want choice of runtime, you use the zip or > use the tools we already provide to build yourself a bespoke installer. Not sure I understand... why would users build themselves an installer? -- Eirik From: Neil C Smith <neilcsm...@apache.org> Reply-To: "dev@netbeans.apache.org" <dev@netbeans.apache.org> Date: Friday, March 21, 2025 at 10:21 AM To: Eirik Bakke <eba...@ultorg.com> Cc: "dev@netbeans.apache.org" <dev@netbeans.apache.org> Subject: Re: Re : Re: heads up: windows installer/uninstaller issues On Fri, 21 Mar 2025 at 14:02, Eirik Bakke <eba...@ultorg.com<mailto:eba...@ultorg.com>> wrote: Here's one idea for how to make an "official" Windows installer, i.e. an installer that is distributed as a convenience binary, officially from Apache NetBeans: 1) Improve the netbeans64.exe launcher so that when it starts and doesn't find the JDK, it prompts the user to select one with a file browser, and remembers the selection for the next time. 2) Package this into an MSI installer using the scripts at https://github.com/eirikbakke/netbeans-msi-example , with only minimal changes to fit into the existing GitHub Actions scripts on the main NetBeans repo. Thoughts on this approach? (In case I decide to work on it.) 1) would be great, as long as it works for the platform too, and would be a major benefit to the zip as well. You might not be the only person looking at launcher code right now, so some coordination of approach might be good. 2) is unnecessary - we can already build a Windows installer using NBPackage - the only thing stopping us switching a long time ago is something like 1). Personally, I'm still in favour of dropping installers here, because of the overhead and because installers without a runtime have other issues. I remain of the view that if you want choice of runtime, you use the zip or use the tools we already provide to build yourself a bespoke installer. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org<mailto:dev-unsubscr...@netbeans.apache.org> For additional commands, e-mail: dev-h...@netbeans.apache.org<mailto:dev-h...@netbeans.apache.org> For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
