This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build: NetBeans IDE Dev (Build web-main-2723-on-100305) VM: Java HotSpot(TM) 64-Bit Server VM, 14.3-b01-101, Java(TM) SE Runtime Environment, 1.6.0_17-b04-248-9M3125 OS: Mac OS X User Comments: pjiricka: Editing Java code. Stacktrace: java.lang.AbstractMethodError: org.netbeans.modules.autoproject.java.AnnotationProcessingQueryImpl$ResultImpl.processorOptions()Ljava/util/Map; at org.netbeans.modules.java.source.indexing.APTUtils.processorOptions(APTUtils.java:133) at org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:676) at org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:637) at org.netbeans.modules.java.source.parsing.CompilationInfoImpl.getJavacTask(CompilationInfoImpl.java:385) at org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:414) at org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:147)
Created attachment 94782 [details] stacktrace
Needs to be fixed in autoproject.
Dusan pushed an empty impl. of the new method: http://hg.netbeans.org/main/contrib/rev/3f7d0f6c1acd http://hg.netbeans.org/main/contrib/rev/d32f552fe255
contrib #3251da2d504d has the real impl.
Created attachment 100179 [details] IDE Log from NetBeans 6.9.
Comment on attachment 100179 [details] IDE Log from NetBeans 6.9. I'm still seeing this in 6.9 final, RC1 and RC2, only with Set instead of Map in the exception. I'm not seeing it in 6.9 beta. java.lang.AbstractMethodError: org.netbeans.modules.autoproject.java.AnnotationProcessingQueryImpl$ResultImpl.annotationProcessingEnabled()Ljava/util/Set;
clintatcomputerorg - you are using org.netbeans.modules.autoproject.java [1.30 nbms-and-javadoc-5083-on-100415] You need to use a later version, at least 1.31, which is updated to the revised API.
This is working fine with the 1.32 plugin from the alpha update center, and according to Jesse it works fine with 1.31 as well. In case anyone else runs into this, pay careful attention to the version of the plugin you are getting from the update center.
*** Bug 187808 has been marked as a duplicate of this bug. ***