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 related or
the same problem.
Since the issue seems to be only reproducible with specific company
network setups and if you really want to get this in, a PR would speed
this up dramatically.
best regards,
michael
On 12.06.22 14:22, Jean-Marc Borer wrote:
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 https://issues.apache.org/jira/browse/NETBEANS-2764 to
GitHub?
Cheers,
JM
On Sat, May 28, 2022 at 3:52 PM Eric Bresie <[email protected]> wrote:
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 regression may have come
back or something did not get merged fully into master.
If one of these matches the concerns
- ( i.e. something like NETBEANS-2764
<https://issues.apache.org/jira/browse/NETBEANS-2764>NoClassDefFoundError
upon Netbeans 11.1-beta2 startup while network is connected with proxy -
but this is a different case), then the details can be migrated into a new
(or copy) the GH Issues
Eric Bresie
[email protected]
On Fri, May 27, 2022 at 10:09 AM Jean-Marc Borer <[email protected]>
wrote:
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. Truffle seems related to GraalVm according to
my
google searches. But still, I have no clue if I am the only one to have
this issue. Then it is probably my fault, but I ignore how to fix it...
On Fri, May 27, 2022 at 3:02 PM Jean-Marc Borer <[email protected]>
wrote:
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 that I regret this.
Lastly, I would be very happy to participate to some extend, but I
really
don't know the technical areas where those bugs are happening. If
someone
could provide me with some hints/guidelines/help I could try, of
course,
to
do my best to identify their origin.
Cheers,
JM
On Fri, May 27, 2022 at 2:12 PM Geertjan Wielenga
<[email protected]> wrote:
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 own hands.
Gj
On Fri, 27 May 2022 at 15:50, Jean-Marc Borer <[email protected]>
wrote:
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:
com/oracle/truffle/api/exception/AbstractTruffleException while
loading
com.oracle.truffle.regex.RegexSyntaxException; see
http://wiki.netbeans.org/DevFaqTroubleshootClassNotFound messages
2) as reported before indexing performance have completely dropped
(even
blocking)
3) Console parsing errors Error in RequestProcessor
org.netbeans.modules.maven.execute.CommandLineOutputHandler$Output
4) when I launch NB plaform apps through Maven, the IDE constantly
reports
that there are running processes at IDE shutdown, which is obviously
completely wrong (I triple checked).
Is it related to OpenJDK17 and that there is no longer nb-javac? I
still
wonder, but my experience is currently bad and I am going to return
to
NB
12.4 with JDK 8...
Has anyone else experienced such issues?
Best regards,
JMB
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
