On 16.10.22 13:35, Neil C Smith wrote:
On Sun, 16 Oct 2022 at 12:08, Michael Bien <[email protected]> wrote:
I think the safest approach would be to upgrade to 36 now and decide
later if we want to take a new build based on 19.0.1. We could also
wait, skip build 36 and go directly to 19.0.1 but this would be riskier.
Agreed. Makes sense to get this in for rc1, even if we need to delay
freeze slightly? Or at least put it through delivery before rc1 is
built?
tbh i would lean towards of not delaying rc1 because of this. (+ there
is the hope that nb-javac might arrive in time). But you are the boss :)
Definitely not! In fact, the point of posing as questions was to put
that call more in your hands than mine. ;-)
However, I will say in all the time of working on releases, nb-javac
has, one way or another, been the cause of the most problems and
delays. I would lean to the earlier in the release process the better
for any changes to it to ensure it gets adequate testing.
We could work towards removing the nb-javac dependency and let the
installer install a matching JDK using the foojay API (user picks the
vendor) and bump the requirements of the zip accordingly.
...
(your community installer is basically already doing this:
https://www.codelerity.com/netbeans/ ;))
Well, there are two conflicting things in play there. I have actually
looked at the feasibility of accessing the Foojay Disco API in eg.
InnoSetup. But the other point of NBPackage and our community
installers is to use native packaging, not relying on any preexisting
JDK for the install process, which complicates that. Much easier for
the community to build them in advance!
agreed. This wouldn't invalidate community installers (I shouldn't have
mentioned installers tbh, its probably not the right place)
What NetBeans could do however is to check early during boot if the
requirements are met. If the aren't, it would launch the disco wizard
(gently).
The platform manager would need a new capability to set the "default
platform". But almost everything else is done or available in some form
already.
once this is working well, all we have to do is to remove nb-javac on
some future release.
-mbien
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
