>Btw. does `netbeans --jdkhome /..../` also work? Yes it does. It never hits the /usr/libexec/java_home logic if that variable is set.
>Mind you, part of me thinks that anyone who upgrades to a new macOS >within a year of release is just asking for trouble anyway ... Agreed, which is why I have not upgraded my personal or work Macs. It is especially true with this release since they are introducing a new architecture with the M1 chips. But many people do blindly upgrade, and some are NetBeans users. > 12.0 LTS, that should be our focus. At the end 12.2 is just "dev version", > but > we should fix 12.0 LTS in my opinion. > Agreed, otherwise the LTS is meaningless. >From Laszlo's other email >Nevertheless, I'd express my disappointment in the communication and the >timing of this issue. Till this date there is no blocker or even >critical issue reported. Laszlo, I understand your frustration and disappointment. I suppose the other alternative could be to modify the macOS installer to insert the jdkhome in the netbeans.conf. I believe that is what is done by the Windows installer. Would that be possible and still pass the current vote? --Christian On Thu, Nov 19, 2020 at 7:40 AM John Mc <mcdonnell.j...@gmail.com> wrote: > > > > > > > > Totally agree, although also agree with Laszlo's annoyance about lack > > of critical / blocking issue, and I think also the 0 votes. Be active > > not passive - call it! :-) > > > > > > Oh I totally understand, and I've not been active recently (Find myself > doing more and more C# at work) around the mailing lists/JIRA, but this > popped up on my radar only last week - which is perfectly understandable > from Lazlo's position as RM. I definitely didn't want to -1 the release > but wanted to call it out in case it was missed by others. Hell if there > was no PR ready I would have +1 without thinking as I don't plan to upgrade > to BigSur until I absolutely need too :) > > Regards > > John >
