I remember Netbeans used to produce file dumps for parsing errors and
ask users to attach them to bug reports... What happened to that?
Having run into many such bugs in the past I usually can't share the
full project because of its commercial nature, or I can't remember what
I did to reproduce the problem.
In developer builds, it would be nice if Netbeans could remember what
steps led to the bug occurring (Exception Reporter used to do this) and
dump something minimal (not the entire project) so it could be attached
to the bug report. Is this a realistic expectation or does something
prevent us from doing this?
Gili
On 2018-03-28 8:48 PM, Eirik Bakke wrote:
Yes, good point, I will try to gather more information and add it to the
JIRAs as each of these bugs reappear. Each of these bugs are intermittent,
so I'm not quite sure how to reproduce them yet.
For a start, I added some sample class files to
https://issues.apache.org/jira/browse/NETBEANS-430 , which reappeared
today.
-- Eirik
On 3/28/18, 6:19 AM, "Jan Lahoda" <lah...@gmail.com> wrote:
Hi Eirik,
Thanks for reporting the bugs. One thing I'd like to point out is that
while it is sometimes possible for someone working on the code to fix a
bug
based just on a stacktrace, having a way to reproduce a problem usually
leads to much faster and efficient fix.
This is particularly true for (nb-)javac, where the problem often is that
something didn't happen even though it should have, and the observable
exception is only a consequence of that.
Jan
On Tue, Mar 27, 2018 at 5:19 PM, Eirik Bakke <eba...@ultorg.com> wrote:
I've now used NetBeans 9.0 Beta for the six weeks since it was
released. I
found several bugs that are potentially related to the nb-javac plugin:
NETBEANS-455<https://issues.apache.org/jira/browse/NETBEANS-455> "The
bytes do not represent a valid class" error while invoking the "Apply
Code
Changes" action
NETBEANS-454<https://issues.apache.org/jira/browse/NETBEANS-454>
AssertionError/"Wrong diagnostic handler ... DeferredDiagnosticHandler"
when opening Java autocomplete
NETBEANS-453<https://issues.apache.org/jira/browse/NETBEANS-453>
"Incorrect number of type arguments" exception during Java editing
NETBEANS-430<https://issues.apache.org/jira/browse/NETBEANS-430>
"Invalid
or deleted file", "Absent Code attribute" exceptions during Java editing
and app/test running
NETBEANS-531<https://issues.apache.org/jira/browse/NETBEANS-531>
"Duplicate method name&signature in class" when running maven app with
CoS
enabled
Might any of these be related to the changes that were made to separate
out nb-javac from the Apache distribution? Or could it be a JDK9 thing?
Note that the Maven projects in question were all JDK8, while the IDE
was
running JDK9.
-- Eirik
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
