Hi Jean,
Please don't migrate anything, there is no point in doing that. The
issue in question was filed against NetBeans 11.1, that was long ago.
Grab fresh stack traces while testing NetBeans 14 if you want to file a
new issue.
Sure you can link to the old jira issue if you think it is
Hello Eric,
Sorry for the late answer. Yes this is exactly the issue I am running into.
I am working behind a corporate proxy that has complex JS scripts in its
PAC file. That may be the reason, I am the only one to have the issue.
How can we migrate
Netbeans project has migrated from JIRA to Github issues.
In the Legacy JIRA (mainly read only) there are a few issues (mainly
closed) that exists (see
https://issues.apache.org/jira/issues/?jql=project%20%3D%20NetBeans%20AND%20text%20~%20Truffle
). Most are Closed but it's possible some sort of
I tried for example to find if there is already a "truffle" issue here:
https://github.com/apache/netbeans/issues
I found nothing yet.
1) Is it the right place to look for issues before reporting (it changed
several times since I followed the project many years ago)?
2) I am not a JVM expert.
Hello Geertjan,
Sure I would ideally. As I have to use NB profesionnaly, I need to use a
stable version on a daily basis and I can hardly access the dev versions
from within my company :-(
Therefore it is very difficult for me to participate easily at those
qualification exercises. Please believe
There’s been issues identified and it’s being looked at. What will you do
to prevent this continuing to happen to you? Maybe join in with early
testing prior to release to flag these issues you encounter and block the
next release until these kinds of issues are fixed?
Global quality is in your
Hi there,
I start thinking that NB 13 has a lot of troubles with OpenJDK 17. I never
had such issues in the past, but since the move to NB 13 I am not that
happy anymore.
1) at start I have a lot of org.graalvm.polyglot.PolyglotException:
java.lang.NoClassDefFoundError:
