You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Neil C Smith <ne...@apache.org> on 2025/05/08 15:47:00 UTC
Community installer migration update
Hi All,
As most of you should be aware, I'm migrating the existing Codelerity
installers to the Friends of Apache NetBeans foundation. These will
be a key source of packages for users as we are not including
installers in the Apache NetBeans 26 release. The community
installers will continue to be built with NBPackage from the official
Apache NetBeans binary zip release.
The migration has included partly automating the installer build
process with GitHub Actions. There is some more work to do leading up
to NetBeans 27. The installer repository includes the build workflows
- https://github.com/Friends-of-Apache-NetBeans/netbeans-installers
Longer term we should be able to open up access to this process to any
other members of the PMC who are interested in helping with it.
Release candidate installers for 26-rc3 are at -
https://github.com/Friends-of-Apache-NetBeans/netbeans-installers/releases/tag/v26rc3-build1
They were built in the workflow at -
https://github.com/codelerity/foan-netbeans-installers/actions/runs/14901730393
This is a copy of the repo (see same hash) so that we can use
Codelerity's secrets for these builds. The NetBeans 26 community
installers will continue to be signed by Codelerity until FoAN has
everything in place to take this over.
The workflow uses a single-source Java file to handle downloading and
validating NBPackage, the NetBeans zip and the Java runtimes. The
build.properties file has the actual links and hashes for the various
artefacts.
There will be a landing page similar to the existing one at
https://www.codelerity.com/netbeans/ once the main release is ready.
This will obviously replace that link on the download page once we get
to NB26 - see current community installers links at
https://netbeans.apache.org/front/main/download/nb25/ - the first two
sections will need revising.
I just thought I'd share an update on progress here, in case of
interest, questions, concerns, etc.
Thanks and best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Neil C Smith <ne...@apache.org>.
Hi,
On Mon, 12 May 2025 at 19:58, Matthias Bläsing
<mb...@doppel-helix.eu.invalid> wrote:
> seems to work good. I tested the deb and exe and both did what they
> promised.
>
> On windows I noticed, that the entry in the uninstaller entry in "Apps
> & features" contains the version ("Apache NetBeans version 26rc3") and
> does not contain the icon, just a generic application icon. The version
> string was present a second time as a line below the title, which does
> not match the other entries. This is not as nice, as it might be, but
> also not a real problem. Deinstallation worked as intended.
Thanks for testing. Much appreciated!
This uninstaller icon issue is a problem with the default template in
NBPackage https://github.com/apache/netbeans-nbpackage/blob/master/src/main/resources/org/apache/netbeans/nbpackage/innosetup/InnoSetup.iss.template
I had noticed this with an earlier community installer. I'm not sure
if something changed with how Windows finds icons for this page.
I think we need to explicitly configure
https://jrsoftware.org/ishelp/index.php?topic=setup_uninstalldisplayicon
and perhaps the related display text.
I'm collating a bunch of issues to work on and get a new release of
NBPackage out before we come to build for NB27. This template, as
with all the templates, is overridable but I'd rather not make that
change now and do some more testing first.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Matthias Bläsing <mb...@doppel-helix.eu.INVALID>.
Hi,
seems to work good. I tested the deb and exe and both did what they
promised.
On windows I noticed, that the entry in the uninstaller entry in "Apps
& features" contains the version ("Apache NetBeans version 26rc3") and
does not contain the icon, just a generic application icon. The version
string was present a second time as a line below the title, which does
not match the other entries. This is not as nice, as it might be, but
also not a real problem. Deinstallation worked as intended.
Thank you!
Greetings
Matthias
Am Donnerstag, dem 08.05.2025 um 16:47 +0100 schrieb Neil C Smith:
> Hi All,
>
> As most of you should be aware, I'm migrating the existing Codelerity
> installers to the Friends of Apache NetBeans foundation. These will
> be a key source of packages for users as we are not including
> installers in the Apache NetBeans 26 release. The community
> installers will continue to be built with NBPackage from the official
> Apache NetBeans binary zip release.
>
> The migration has included partly automating the installer build
> process with GitHub Actions. There is some more work to do leading up
> to NetBeans 27. The installer repository includes the build workflows
> - https://github.com/Friends-of-Apache-NetBeans/netbeans-installers
> Longer term we should be able to open up access to this process to any
> other members of the PMC who are interested in helping with it.
>
> Release candidate installers for 26-rc3 are at -
> https://github.com/Friends-of-Apache-NetBeans/netbeans-installers/releases/tag/v26rc3-build1
>
> They were built in the workflow at -
> https://github.com/codelerity/foan-netbeans-installers/actions/runs/14901730393
> This is a copy of the repo (see same hash) so that we can use
> Codelerity's secrets for these builds. The NetBeans 26 community
> installers will continue to be signed by Codelerity until FoAN has
> everything in place to take this over.
>
> The workflow uses a single-source Java file to handle downloading and
> validating NBPackage, the NetBeans zip and the Java runtimes. The
> build.properties file has the actual links and hashes for the various
> artefacts.
>
> There will be a landing page similar to the existing one at
> https://www.codelerity.com/netbeans/ once the main release is ready.
> This will obviously replace that link on the download page once we get
> to NB26 - see current community installers links at
> https://netbeans.apache.org/front/main/download/nb25/ - the first two
> sections will need revising.
>
>
> I just thought I'd share an update on progress here, in case of
> interest, questions, concerns, etc.
>
> Thanks and best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Carl Mosca <ca...@gmail.com>.
Ok thank you Stan.
Regards,
Carl
On Fri, May 23, 2025 at 10:28 AM Giles Winstanley <st...@snaq.net> wrote:
> More or less nothing, I was just being overly finicky about it. My fork
> turns out to be based on your old f23a61e commit (2 Aug 2018), so yours
> has changed considerably more than mine since then. The only obvious
> functional difference I spot in the update are:
>
> *install.sh*
> - Updated application name to be unversioned (as current release)
> - Updated link to binary to use "/netbeans/" instead of
> "/NetBeans/" (for unlikely case-sensitive FS scenario)
>
> *Info.plist
> * - Updated CFBundleName/CFBundleDisplayName to be unversioned (as
> current release)
> - Updated CFBundleIdentifier to same as release (prevent multiple
> NB instances changing same config?)
> - Updated CFBundleSignature to same as release (no idea if this
> makes any difference; guessing not)
> - Removed
>
> CFBundleDocumentTypes/NSHighResolutionCapable/NSSupportsAutomaticGraphicsSwitching
>
> My primary thinking was just to ensure multiple similar versions
> wouldn't accidentally be running, to avoid configuration directory
> clashes. The removal of the 3 Info.plist keys seems fairly trivial, and
> I'm imagining the last two are by default set now anyway. I imagine your
> current script works fine as it is.
>
> Stan
>
> On 23/05/2025 12:51, Carl Mosca wrote:
> > Ah, not look at that script in a good bit Stan. Now you have me curious
> > about what tweaks were needed.
> >
> > Carl
> >
> > On Fri, May 23, 2025 at 7:28 AM Giles Winstanley<st...@snaq.net> wrote:
> >
> >> The potential for it to be marked as broken was something I had in mind,
> >> but curiously it seems to have worked fine. And "doing all that" amounts
> >> to essentially two/three terminal commands, so little lost if it turns
> >> out not to work down the line. In case anyone else wants to try:
> >>
> >> # Remove bundled JDK & compiled launcher
> >> cd "/Applications/Apache NetBeans.app/Contents" && sudo rm -rf
> Home
> >> MacOS/netbeans
> >> # Create link to script-based launcher
> >> sudo ln -s ../Resources/netbeans/bin/netbeans MacOS/
> >>
> >> I'll stick with trying this version for now, as at least it should have
> >> the various binaries signed. As it happens I found I've also still got
> >> my old fork of Carl Mosca's netbeans-macos-bundle script lying around,
> >> which seems to have successfully bundled it from the binary zip with a
> >> couple of small tweaks, so if the above doesn't work I'll try that
> instead.
> >>
> >> For now at least...problem solved.
> >> Stan
> >>
> >>
> >>
> >> On 22/05/2025 16:46, Neil C Smith wrote:
> >>> On Thu, 22 May 2025 at 16:42, Giles Winstanley<st...@snaq.net> wrote:
> >>>> Fair enough; turns out after a quick test it should be fine to delete
> >>>> the Home directory & netbeans binary within the bundle, then create a
> >>>> symbolic link to the usual netbeans script, as older scripts used to
> do.
> >>>> I'm half expecting some permissions issues to pop up, but hopefully
> this
> >>>> will work out.
> >>> This will probably lead to the app being marked broken.
> >>>
> >>> If you've doing all that, just use the zip instead.
> >>>
> >>> Neil
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail:dev-unsubscribe@netbeans.apache.org
> >>> For additional commands, e-mail:dev-help@netbeans.apache.org
> >>>
> >>> For further information about the NetBeans mailing lists, visit:
> >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:dev-unsubscribe@netbeans.apache.org
> >> For additional commands, e-mail:dev-help@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >>
>
Re: Community installer migration update
Posted by Giles Winstanley <st...@snaq.net>.
More or less nothing, I was just being overly finicky about it. My fork
turns out to be based on your old f23a61e commit (2 Aug 2018), so yours
has changed considerably more than mine since then. The only obvious
functional difference I spot in the update are:
*install.sh*
- Updated application name to be unversioned (as current release)
- Updated link to binary to use "/netbeans/" instead of
"/NetBeans/" (for unlikely case-sensitive FS scenario)
*Info.plist
* - Updated CFBundleName/CFBundleDisplayName to be unversioned (as
current release)
- Updated CFBundleIdentifier to same as release (prevent multiple
NB instances changing same config?)
- Updated CFBundleSignature to same as release (no idea if this
makes any difference; guessing not)
- Removed
CFBundleDocumentTypes/NSHighResolutionCapable/NSSupportsAutomaticGraphicsSwitching
My primary thinking was just to ensure multiple similar versions
wouldn't accidentally be running, to avoid configuration directory
clashes. The removal of the 3 Info.plist keys seems fairly trivial, and
I'm imagining the last two are by default set now anyway. I imagine your
current script works fine as it is.
Stan
On 23/05/2025 12:51, Carl Mosca wrote:
> Ah, not look at that script in a good bit Stan. Now you have me curious
> about what tweaks were needed.
>
> Carl
>
> On Fri, May 23, 2025 at 7:28 AM Giles Winstanley<st...@snaq.net> wrote:
>
>> The potential for it to be marked as broken was something I had in mind,
>> but curiously it seems to have worked fine. And "doing all that" amounts
>> to essentially two/three terminal commands, so little lost if it turns
>> out not to work down the line. In case anyone else wants to try:
>>
>> # Remove bundled JDK & compiled launcher
>> cd "/Applications/Apache NetBeans.app/Contents" && sudo rm -rf Home
>> MacOS/netbeans
>> # Create link to script-based launcher
>> sudo ln -s ../Resources/netbeans/bin/netbeans MacOS/
>>
>> I'll stick with trying this version for now, as at least it should have
>> the various binaries signed. As it happens I found I've also still got
>> my old fork of Carl Mosca's netbeans-macos-bundle script lying around,
>> which seems to have successfully bundled it from the binary zip with a
>> couple of small tweaks, so if the above doesn't work I'll try that instead.
>>
>> For now at least...problem solved.
>> Stan
>>
>>
>>
>> On 22/05/2025 16:46, Neil C Smith wrote:
>>> On Thu, 22 May 2025 at 16:42, Giles Winstanley<st...@snaq.net> wrote:
>>>> Fair enough; turns out after a quick test it should be fine to delete
>>>> the Home directory & netbeans binary within the bundle, then create a
>>>> symbolic link to the usual netbeans script, as older scripts used to do.
>>>> I'm half expecting some permissions issues to pop up, but hopefully this
>>>> will work out.
>>> This will probably lead to the app being marked broken.
>>>
>>> If you've doing all that, just use the zip instead.
>>>
>>> Neil
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:dev-unsubscribe@netbeans.apache.org
>>> For additional commands, e-mail:dev-help@netbeans.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail:dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
Re: Community installer migration update
Posted by Carl Mosca <ca...@gmail.com>.
Ah, not look at that script in a good bit Stan. Now you have me curious
about what tweaks were needed.
Carl
On Fri, May 23, 2025 at 7:28 AM Giles Winstanley <st...@snaq.net> wrote:
> The potential for it to be marked as broken was something I had in mind,
> but curiously it seems to have worked fine. And "doing all that" amounts
> to essentially two/three terminal commands, so little lost if it turns
> out not to work down the line. In case anyone else wants to try:
>
> # Remove bundled JDK & compiled launcher
> cd "/Applications/Apache NetBeans.app/Contents" && sudo rm -rf Home
> MacOS/netbeans
> # Create link to script-based launcher
> sudo ln -s ../Resources/netbeans/bin/netbeans MacOS/
>
> I'll stick with trying this version for now, as at least it should have
> the various binaries signed. As it happens I found I've also still got
> my old fork of Carl Mosca's netbeans-macos-bundle script lying around,
> which seems to have successfully bundled it from the binary zip with a
> couple of small tweaks, so if the above doesn't work I'll try that instead.
>
> For now at least...problem solved.
> Stan
>
>
>
> On 22/05/2025 16:46, Neil C Smith wrote:
> > On Thu, 22 May 2025 at 16:42, Giles Winstanley <st...@snaq.net> wrote:
> >> Fair enough; turns out after a quick test it should be fine to delete
> >> the Home directory & netbeans binary within the bundle, then create a
> >> symbolic link to the usual netbeans script, as older scripts used to do.
> >> I'm half expecting some permissions issues to pop up, but hopefully this
> >> will work out.
> > This will probably lead to the app being marked broken.
> >
> > If you've doing all that, just use the zip instead.
> >
> > Neil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
--
Carl J. Mosca
Re: Community installer migration update
Posted by Neil C Smith <ne...@apache.org>.
On Fri, 23 May 2025 at 12:28, Giles Winstanley <st...@snaq.net> wrote:
> # Remove bundled JDK & compiled launcher
...
> # Create link to script-based launcher
> sudo ln -s ../Resources/netbeans/bin/netbeans MacOS/
Just for the record, that Swift launcher doesn't do a lot aside from
delegate to the script launcher -
https://github.com/apache/netbeans-nbpackage/blob/master/src/main/resources/org/apache/netbeans/nbpackage/macos/main.swift.template
It's just a necessity for distribution and various access permissions to work.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Giles Winstanley <st...@snaq.net>.
The potential for it to be marked as broken was something I had in mind,
but curiously it seems to have worked fine. And "doing all that" amounts
to essentially two/three terminal commands, so little lost if it turns
out not to work down the line. In case anyone else wants to try:
# Remove bundled JDK & compiled launcher
cd "/Applications/Apache NetBeans.app/Contents" && sudo rm -rf Home
MacOS/netbeans
# Create link to script-based launcher
sudo ln -s ../Resources/netbeans/bin/netbeans MacOS/
I'll stick with trying this version for now, as at least it should have
the various binaries signed. As it happens I found I've also still got
my old fork of Carl Mosca's netbeans-macos-bundle script lying around,
which seems to have successfully bundled it from the binary zip with a
couple of small tweaks, so if the above doesn't work I'll try that instead.
For now at least...problem solved.
Stan
On 22/05/2025 16:46, Neil C Smith wrote:
> On Thu, 22 May 2025 at 16:42, Giles Winstanley <st...@snaq.net> wrote:
>> Fair enough; turns out after a quick test it should be fine to delete
>> the Home directory & netbeans binary within the bundle, then create a
>> symbolic link to the usual netbeans script, as older scripts used to do.
>> I'm half expecting some permissions issues to pop up, but hopefully this
>> will work out.
> This will probably lead to the app being marked broken.
>
> If you've doing all that, just use the zip instead.
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 22 May 2025 at 16:59, James Gosling <ja...@norquay.com> wrote:
> If anyone is interested, I have a shell script that finds the most recent netbeans from your downloads directory (which is what you get when you click on the .zip link on the netbeans site) and builds an app from it and installs it as ~/Applications/NetBeans.app. It uses the local java installation. No app signing required. No macos binary. I could put it on homebrew.
That would be great. Thanks, James.
Documenting these things, and things such as local desktop files on
Linux (eg. https://lists.apache.org/thread/2bh3zs0cddgt1ttft6vgjpdg4o8jndjk
) or providing simple scripts to work with the zips are the right way
to handle this in my opinion.
There's a world of difference between what people can and should be
able to flexibly configure on their own machines, vs getting an
installer past Apple's notarization process.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by James Gosling <ja...@norquay.com>.
If anyone is interested, I have a shell script that finds the most recent netbeans from your downloads directory (which is what you get when you click on the .zip link on the netbeans site) and builds an app from it and installs it as ~/Applications/NetBeans.app. It uses the local java installation. No app signing required. No macos binary. I could put it on homebrew.
Re: Community installer migration update
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 22 May 2025 at 16:42, Giles Winstanley <st...@snaq.net> wrote:
> Fair enough; turns out after a quick test it should be fine to delete
> the Home directory & netbeans binary within the bundle, then create a
> symbolic link to the usual netbeans script, as older scripts used to do.
> I'm half expecting some permissions issues to pop up, but hopefully this
> will work out.
This will probably lead to the app being marked broken.
If you've doing all that, just use the zip instead.
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Giles Winstanley <st...@snaq.net>.
Fair enough; turns out after a quick test it should be fine to delete
the Home directory & netbeans binary within the bundle, then create a
symbolic link to the usual netbeans script, as older scripts used to do.
I'm half expecting some permissions issues to pop up, but hopefully this
will work out.
Stan
On 22/05/2025 15:53, Neil C Smith wrote:
> On Thu, 22 May 2025 at 15:39, Giles Winstanley <st...@snaq.net> wrote:
>> Just wondering if there's provision for a friends-of-apache-netbeans
>> build for macOS which doesn't bundle a JDK? Given the history of using
>> an already-installed JDK for running NB, and the reality that most
>> people using it will have 1+ JDKs already installed, it seems a good
>> option to have such a bundle available for download, rather than
>> needlessly occupy yet another 250MB+ of valuable drive space.
> Short answer, no.
>
> The JDK in the installer is part of the package, not exposed globally,
> and is signed with the same certificate, hardened runtime
> entitlements, etc. as the rest of the IDE. Having a runtime in the
> package is a good thing, and cuts down on the support requirements.
> Other IDEs do the same as far as I know.
>
> If you want to run NetBeans on a JDK of choice then you can use the
> binary zip, or even build your own installer with/without JDK using
> NBPackage.
>
> Any installer without JDK could be distributed here directly, so it's
> unlikely it would come from FoAN. It would, however, need a PMC
> member with a desire to make it happen! I personally think it's a bad
> idea, which is why I personally stopped putting time into it.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 22 May 2025 at 15:39, Giles Winstanley <st...@snaq.net> wrote:
> Just wondering if there's provision for a friends-of-apache-netbeans
> build for macOS which doesn't bundle a JDK? Given the history of using
> an already-installed JDK for running NB, and the reality that most
> people using it will have 1+ JDKs already installed, it seems a good
> option to have such a bundle available for download, rather than
> needlessly occupy yet another 250MB+ of valuable drive space.
Short answer, no.
The JDK in the installer is part of the package, not exposed globally,
and is signed with the same certificate, hardened runtime
entitlements, etc. as the rest of the IDE. Having a runtime in the
package is a good thing, and cuts down on the support requirements.
Other IDEs do the same as far as I know.
If you want to run NetBeans on a JDK of choice then you can use the
binary zip, or even build your own installer with/without JDK using
NBPackage.
Any installer without JDK could be distributed here directly, so it's
unlikely it would come from FoAN. It would, however, need a PMC
member with a desire to make it happen! I personally think it's a bad
idea, which is why I personally stopped putting time into it.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Giles Winstanley <st...@snaq.net>.
Hi folks,
Just wondering if there's provision for a friends-of-apache-netbeans
build for macOS which doesn't bundle a JDK? Given the history of using
an already-installed JDK for running NB, and the reality that most
people using it will have 1+ JDKs already installed, it seems a good
option to have such a bundle available for download, rather than
needlessly occupy yet another 250MB+ of valuable drive space.
Thanks, Stan
On 08/05/2025 16:47, Neil C Smith wrote:
> Hi All,
>
> As most of you should be aware, I'm migrating the existing Codelerity
> installers to the Friends of Apache NetBeans foundation. These will
> be a key source of packages for users as we are not including
> installers in the Apache NetBeans 26 release. The community
> installers will continue to be built with NBPackage from the official
> Apache NetBeans binary zip release.
>
> The migration has included partly automating the installer build
> process with GitHub Actions. There is some more work to do leading up
> to NetBeans 27. The installer repository includes the build workflows
> - https://github.com/Friends-of-Apache-NetBeans/netbeans-installers
> Longer term we should be able to open up access to this process to any
> other members of the PMC who are interested in helping with it.
>
> Release candidate installers for 26-rc3 are at -
> https://github.com/Friends-of-Apache-NetBeans/netbeans-installers/releases/tag/v26rc3-build1
>
> They were built in the workflow at -
> https://github.com/codelerity/foan-netbeans-installers/actions/runs/14901730393
> This is a copy of the repo (see same hash) so that we can use
> Codelerity's secrets for these builds. The NetBeans 26 community
> installers will continue to be signed by Codelerity until FoAN has
> everything in place to take this over.
>
> The workflow uses a single-source Java file to handle downloading and
> validating NBPackage, the NetBeans zip and the Java runtimes. The
> build.properties file has the actual links and hashes for the various
> artefacts.
>
> There will be a landing page similar to the existing one at
> https://www.codelerity.com/netbeans/ once the main release is ready.
> This will obviously replace that link on the download page once we get
> to NB26 - see current community installers links at
> https://netbeans.apache.org/front/main/download/nb25/ - the first two
> sections will need revising.
>
>
> I just thought I'd share an update on progress here, in case of
> interest, questions, concerns, etc.
>
> Thanks and best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Community installer migration update
Posted by Michael Bien <mb...@gmail.com>.
On 5/8/25 17:47, Neil C Smith wrote:
> Hi All,
>
> As most of you should be aware, I'm migrating the existing Codelerity
> installers to the Friends of Apache NetBeans foundation. These will
> be a key source of packages for users as we are not including
> installers in the Apache NetBeans 26 release. The community
> installers will continue to be built with NBPackage from the official
> Apache NetBeans binary zip release.
>
> The migration has included partly automating the installer build
> process with GitHub Actions. There is some more work to do leading up
> to NetBeans 27. The installer repository includes the build workflows
> - https://github.com/Friends-of-Apache-NetBeans/netbeans-installers
> Longer term we should be able to open up access to this process to any
> other members of the PMC who are interested in helping with it.
>
> Release candidate installers for 26-rc3 are at -
> https://github.com/Friends-of-Apache-NetBeans/netbeans-installers/releases/tag/v26rc3-build1
nice! gave the .rpm a quick try and everything worked great.
>
> They were built in the workflow at -
> https://github.com/codelerity/foan-netbeans-installers/actions/runs/14901730393
> This is a copy of the repo (see same hash) so that we can use
> Codelerity's secrets for these builds. The NetBeans 26 community
> installers will continue to be signed by Codelerity until FoAN has
> everything in place to take this over.
>
> The workflow uses a single-source Java file to handle downloading and
> validating NBPackage, the NetBeans zip and the Java runtimes. The
> build.properties file has the actual links and hashes for the various
> artefacts.
>
> There will be a landing page similar to the existing one at
> https://www.codelerity.com/netbeans/ once the main release is ready.
> This will obviously replace that link on the download page once we get
> to NB26 - see current community installers links at
> https://netbeans.apache.org/front/main/download/nb25/ - the first two
> sections will need revising.
NB26 dl page draft PR is at https://github.com/apache/netbeans-antora-site/pull/41
-mbien
>
>
> I just thought I'd share an update on progress here, in case of
> interest, questions, concerns, etc.
>
> Thanks and best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists