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 # : 200410101800 ] [ JDK VERSION : J2SE 1.5.0 ] The error annotations have disappeared in the latest daily builds (10/10 and 10/11). Modify an existing method and pass in an invalid type of parameter. Save the file. Wait... no error annotations appear. Other types of annotations seem unaffected.
Jason, sorry, but I am not able to reproduce it following the steps you have provided. Could you please provide more exact steps to reproduce? Since it is not reproducible and it does not result in any code damage and user is not blocked from using the IDE, I am lowering the priority to P3.
After further testing, this issue seems to be related to http://www.netbeans.org/issues/show_bug.cgi?id=49951. If I restart the IDE and do not allow issue 49951 to occur, I also cannot reproduce this behavior. The way I reproduce this behavior is as follows: have some method declared: public void amethod (AParameter aparameter) invoke the method as: BParameter bparameter = new BParameter () ; //where BParameter is not derived from AParameter this.amethod (bparameter) ; After saving the file and waiting, I never receive the error annotation. I believe a fix for http://www.netbeans.org/issues/show_bug.cgi?id=49951 is due in tomorrow's daily. I will retest then.
Jason, can you reproduce it in latest build?
I can still reproduce this in the latest build (Oct 12) without getting issue # 49951 to occur. Occasionally the attached exceptions are thrown when trying to reproduce this behavior. It's unclear whether I should file a new issue for the attached exceptions. Please advise.
Created attachment 18263 [details] exceptions from console
The attached exception was fixed (see issue 50318, which contains a little bit different stacktrace, but in fact it was caused by the same bug). The fix will be part of tomorrows build. So, you don't need to file a separate report.
The problem seems to be fixed.
Verified fixed in build 200410271800
Reorganization of java component