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 >
