On Mon, 23 Feb 2026 at 22:08, Pieter van den Hombergh <[email protected]> wrote: > Interesting idea, but with some consequences: > I do not think it would be a good idea to have multiple variants under > different urls. I would increase the maintenance for the netbeans.org > website and would split the overview. so one installers site please.
Restricting to one site is not going to happen. Listing under the community installers section has always been open to any committer or PMC member who wants to provide release compliant binaries. Snap, which Laszlo produces, is listed there too, btw, not just my installers. More the merrier in my opinion, at least until we need to paginate the list! Believe me, the maintenance overhead for the netbeans.apache.org website of these links is negligible compared to the overheads of the release process. Community installers are provided by people with commit rights, so they can manage any maintenance themselves. And the release website overhead seems to mainly involve fighting with Jenkins - got there in the end! :-) > At the moment the process of packaging and signing is fully automated ... Yes, as is the Codelerity build. Unfortunately, what seems to have been lost in your changes is the ability for it to work without signing or as a template? It's one reason I decided to keep my repo active. Multiple people contacted me last year about alternative NetBeans, JDKs, parallel installs, etc. I could just advise them to fork the repo, specify which line to change, and trigger their own alternative installer. You can still see a couple of them in the FoAN forks list still. It's probably a better option than trying to look at supporting too many combinations. 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
