+0.1
I have (potentially) destroyed my Mac by upgrading to Big Sur just to find
out that my setup (e.g. no global JDK at all) isn't suitable for testing
the reported problem. All I can confirm is that using `--jdkhome
/path/to/jdk` works as always. I have no problems running NetBeans 12.2 RC3
Laszlo, thanks for your hard work!
+1
Tested running binary on macOS Catalina and macOS Big Sur.
Built Maven Java app
---
>Log Session: Thursday, November 19, 2020 at 2:51:55 PM Eastern Standard
Time
>System Info:
Dear Apache NetBeans community,
The third, and hopefully FINAL release candidate of Apache NetBeans 12.2
is available.
This one blocker, one trivial and one documentation fix is in this
release as of:
[NETBEANS-5042] Launcher can't find Java Home on MacOS BigSur --
Just a note about not filing a bug report. The bug is with Apple, I filed
a bug with them while Big Sur was still in beta - hoping that it would be
addressed before the release. While testing NB 12.2, there were no
installers and I always copy the binaries over my existing install and then
Dear all,
The vote has been cancelled, due to the BigSur JavaHome issue.
We have a PR that fixes that, so there will be a an express round for an
rc3. Then a new vote would be issued on 20th or 21st of November.
--
Laszlo Kishalmi
>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
> I'm about to cancel the current vote on NetBeans 12.2 release as it
> > seems we have a fix now for the MacOS launcher.
>
> Understandable, but it opens pandora's box: Can we get a few more fixes in
> for
> the VSCode support, please?
>
We have prepared
>
>
>
> 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
0 (binding)
- I agree that it makes sense to include the Big Sur issues by including the PR
in this release
Thanks for all of your hard work and time.
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau
On Thu, 19 Nov 2020 at 08:33, John Mc wrote:
> > 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.
> >
> Is it just a "dev version"? Or is it just a release that has a shorter
> support cycle?
Definitely the latter! In
>
>
> 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.
>
>
Is it just a "dev version"? Or is it just a release that has a shorter
support cycle?
Anyways that besides the point, we're releasing software, that software in
my
11 matches
Mail list logo
