Looks like I did not. Everything seems to work again once nb-javac is
uninstalled.
Many thanks Jan!
On 7/25/21 12:06 AM, Jan Lahoda wrote:
Do you have an up-to-date build of NetBeans? This has been fixed by this
commit some time ago:
https://github.com/apache/netbeans/commit/43338016d661b743
Do you have an up-to-date build of NetBeans? This has been fixed by this
commit some time ago:
https://github.com/apache/netbeans/commit/43338016d661b74317892298d88b0a32663adb05
Jan
On Sun, Jul 25, 2021 at 6:40 AM Ty Young wrote:
> Thanks for verifying.
>
>
> Netbeans is even more borked withou
Thanks for verifying.
Netbeans is even more borked without nb-javac for me. On load, all the
projects that were open are closed except for the parent pom objects.
Attempting to right click on a file under "Projects" on the left side
does nothing. Files under "Projects" are still marked with e
Hi Ty,
Sorry, I missed this e-mail. I just tried a build from the current NetBeans
master and Panama's foreign-memaccess+abi branch, using a simple Maven
project. I can see the problem, but only with nb-javac installed. Given
nb-javac is based on the last released JDK (i.e. JDK 16) and Panama is J
Were* *sigh*
On 7/24/21 9:08 PM, Ty Young wrote:
Where you able to reproduce it by any chance?
On 7/13/21 10:18 AM, Ty Young wrote:
You may need to build from this branch, which I use:
https://github.com/openjdk/panama-foreign/tree/foreign-memaccess+abi
The default branch "foreign-jextra
Where you able to reproduce it by any chance?
On 7/13/21 10:18 AM, Ty Young wrote:
You may need to build from this branch, which I use:
https://github.com/openjdk/panama-foreign/tree/foreign-memaccess+abi
The default branch "foreign-jextract" is based on
foreign-memaccess+abi and is update
You may need to build from this branch, which I use:
https://github.com/openjdk/panama-foreign/tree/foreign-memaccess+abi
The default branch "foreign-jextract" is based on foreign-memaccess+abi
and is updated less often.
This build is then used as the system JDK(AKA JAVA_HOME). The project
Hi Ty,
Do you have more information on how to reproduce (i.e. how to setup the IDE
and the projects to see the problem). I tried to run a (very) recent build
on the Panama branch, and create a simple project, and I didn't see the
FatalError, so there is something other I need to do.
Thanks,
J
ut in a lot
of work and their efforts seem to be for naught.
I'm not saying that there aren't people who do yeoman's work. But a
realistic view of the project feels lacking, or maybe that's just the
public forums.
-ernie
Forwarded Message
Subject: Re
On Sun, Jul 11, 2021 at 2:18 PM Ty Young wrote:
> Maybe a bit too negative, even for me. Netbeans has seen various
> improvements over the years although it does feel slow and small. I
> suppose that's just because of it being purely Open Source and not
> having a paid for version with which full
On 12.07.21 11:22, Neil C Smith wrote:
On Mon, 12 Jul 2021 at 03:54, Michael Bien wrote:
So lets say 12.5 is
out and fully supports 17,
Hopefully 12.5 will support JDK 17 well, but fully supported should be
expected in 12.6 - ie. first release tried and tested after JDK 17
released.
thanks
er
available for older stuff. Some people put in a lot of work and their
efforts seem to be for naught.
I'm not saying that there aren't people who do yeoman's work. But a
realistic view of the project feels lacking, or maybe that's just the
public forums.
-ernie
-
That's right, was going to point this out as well -- NetBeans officially
supports a JDK release at the time of its actual release, which is
September in this case (see foojay.io for the Java Release Roadmap), which
is 12.6, not 12.5.
Gj
On Mon, Jul 12, 2021 at 11:24 AM Neil C Smith wrote:
> On
On Mon, 12 Jul 2021 at 03:54, Michael Bien wrote:
> So lets say 12.5 is
> out and fully supports 17,
Hopefully 12.5 will support JDK 17 well, but fully supported should be
expected in 12.6 - ie. first release tried and tested after JDK 17
released.
> Alone due to the javac dependency is unreali
and their efforts seem to be for naught.
I'm not saying that there aren't people who do yeoman's work. But a
realistic view of the project feels lacking, or maybe that's just the
public forums.
-ernie
-------- Forwarded Message ----
Subject: Re: NB and JDK 17 - OpenJDK
for older stuff. Some people put in a lot of work and their
> > efforts seem to be for naught.
> >
> > I'm not saying that there aren't people who do yeoman's work. But a
> > realistic view of the project feels lacking, or maybe that's just the
>
rk. But a
realistic view of the project feels lacking, or maybe that's just the
public forums.
-ernie
---- Forwarded Message ----
Subject: Re: NB and JDK 17 - OpenJDK Quality Outreach
Date: Sun, 11 Jul 2021 20:14:10 +0200
From: Jeremy Cavanagh
To: Ty Young
Hi Ty Young,
Ther
e project feels lacking, or maybe that's just the
> public forums.
>
> -ernie
>
> >
> >
> >
> > Forwarded Message
> > Subject: Re: NB and JDK 17 - OpenJDK Quality Outreach
> > Date: Sun, 11 Jul 2021 20:14:10 +0200
> > From: Jeremy Cavanagh
o yeoman's work. But a
realistic view of the project feels lacking, or maybe that's just the
public forums.
-ernie
Forwarded Message --------
Subject: Re: NB and JDK 17 - OpenJDK Quality Outreach
Date: Sun, 11 Jul 2021 20:14:10 +0200
From: Jeremy Cavanagh
To: Ty Young
Hi T
That's fair. Apologies.
On 7/11/21 1:15 PM, Jeremy Cavanagh wrote:
Forwarded Message
Subject: Re: NB and JDK 17 - OpenJDK Quality Outreach
Date: Sun, 11 Jul 2021 20:14:10 +0200
From: Jeremy Cavanagh
To: Ty Young
Hi Ty Young,
There's no need to be rude.
Forwarded Message
Subject: Re: NB and JDK 17 - OpenJDK Quality Outreach
Date: Sun, 11 Jul 2021 20:14:10 +0200
From: Jeremy Cavanagh
To: Ty Young
Hi Ty Young,
There's no need to be rude. The reason people are asked to join the
group is to get involved and help pr
The deprecation of the SecurityManager is definitely one of the items
requiring parts of NetBeans to be reworked. Whenever the JDK drops
features, there’s likely to be an impact on its tooling, such as NetBeans.
Gj
On Sun, 11 Jul 2021 at 19:11, Ty Young wrote:
> I seem to recall a thread on the
I seem to recall a thread on the official OpenJDK mailing lists claiming
that there is no difference between LTS and non-LTS for the purposes of
the JDK's development and that people shouldn't hesitate(or not) to make
a change because a particular release is LTS.
Anyway, sort of getting off-t
Indeed, JDK 17 support is being worked on.
And sometimes NetBeans may work with a particular JDK before that JDK is
released, without anything needing to be changed in NetBeans at all. But
not always, typically not with LTS releases, such as JDK 17, which come
with a lot of changes, impacting NetB
I'm aware the sky is blue and water is wet, thanks. You had said that
JDK 17 was being worked on. Clearly that was a lie. What's the point of
forcing people to join a dev list just so you tell them this?
Netbeans has never technically supported in-dev builds but they've
always generally worke
Indeed, NetBeans does not support JDK 18 (also not JDK 17) at this stage.
Gj
On Sun, 11 Jul 2021 at 04:12, Ty Young wrote:
> >
>
>
> Hi,
>
>
> I use JDK 18 builds of Project Panama[1] that Netbeans does not work
> properly with. All classes with JDK 18 have errors with the package
> statement
>
Hi,
I use JDK 18 builds of Project Panama[1] that Netbeans does not work
properly with. All classes with JDK 18 have errors with the package
statement claiming that:
Cannot access java.lang
Fatal Error: Unable to find package java.lang in classpath or
bootclasspath.
This happen
12.5 is targeted for JDK 17.
12.4 has not / cannot be applicable to JDK 17, to the extent that that
combination can work, that is purely a coincidence.
Can you consider not trying the 12.4/JDK 17 combination at all anymore
(that only creates confusion) and focus only on 12.5 instead?
Gj
On Sat
I am running some of my sample code from my courses with NB 12.4 and JDK 17 ea
26. Initially I could not get this to work as I mentioned in a previous email.
In response Ludovic wrote that he filed:
[NETBEANS-5775] [1] for that NoSuchMethodError and Jan Lahoda is working on a
PR to fix it [2].
29 matches
Mail list logo
