Hi,
NetBeans relies on an embedded Graal.js (which includes Truffle
libraries) for parsing javascript PAC proxy configuration. There was a
bug in NB-13 until almost NB14 release in bad metadata in a wrapper jar
that blocked some classes from loading - they were moved in Truffle to
another package.
NB14 should be fine AFAIK (or at least I hope - I checked this when
signing off the release).
The workaround for the earlier releases is to specify proxy settings
manually in the Tools | Options; the js support is only attempted if the
autoconfiguration is used && PAC resource is actually available at the
runtime.
-S.
Dne 12. 06. 22 v 11:05 Jean-Marc Borer napsal(a):
Ok so before filing a bug, I want to retry with NB 14. I was looking for
the packages released for the vote. They are no longer available. Do you
know where I can find them?
JM
PS: I am working in a very complicated (secured) professional environment
and I clearly push NB into certain limits especially what relates to secure
proxies, certificate handling and white listed sites. At home, I don't have
such constraints and would certainly not notice these issues.
We still use NB platform even for new apps. My concern is therefore that
the platform properly runs in our environment and it starts with NB IDE.
Currently I still use 12.4 with JDK 8, which is rather robust.
Unfortunately I still cannot say the same with NB 13 and JDK 17, but I try
to make it happen as much as I can, but there are a lot of areas in the IDE
that clearly don't know yet to properly diagnose my issues.
On Sun, Jun 12, 2022 at 10:55 AM Geertjan Wielenga
<geertjan.wiele...@googlemail.com.invalid> wrote:
Yes, I’m surprised too. And obviously NetBeans is not supposed to run only
on GraalVM, you know the answer to that question, and that this is a bug.
Gj
On Sun, 12 Jun 2022 at 10:53, Jean-Marc Borer <jmbo...@gmail.com> wrote:
Hello Geertjan,
Well yes and no. I am surprised that NB seems to, somehow, rely on
Truffle
classes during startup. As I am not a JVM expert, I was not knowing what
Truffle is. By the way, is NB now supposed to only run on GraalVM? Same
question for NB platform based applications, which is actually my
concern.
JM
On Sun, Jun 12, 2022 at 10:45 AM Geertjan Wielenga
<geertjan.wiele...@googlemail.com.invalid> wrote:
You’re surprised that messages about missing Truffle classes do not
appear
when you use GraalVM?
Gj
On Sun, 12 Jun 2022 at 10:42, Jean-Marc Borer <jmbo...@gmail.com>
wrote:
Hello all,
Since I had several issues with NB 13 (see
https://github.com/apache/netbeans/issues/4050), I tried different
JVMs.
I notice that the only one not generating warnings in the log (for
example
related to missing Truffle classes) is GraalVM 17. I have to say
that I
am
a bit surprise in this regard since it is not specified anywhere and
this
disables the possibility to design or use UI previews with JFX
components.
Is Netbeans not supposed to run on any flavor (JVM) 11+?
Best regards,
JMB
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
