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.
[release40-200411041919, JDK 1.4.2_06] If there is error in source in editor and user does build of the project that fails and then clicks on the error in output window then the editor shows double error annotation despite there is only one error on the line.
One error icon is parser annotation, second icon is Ant Build Errors. Unfortunatelly they have the same icon and this can cause confusion. Resolving as invalid. Try to file an issue to appropriate module (ant/java) for icon changing. Thanks.
I know what those icons mean, but it seems to me as quite useless (and possibly confusing) to show two error icons (even in the case they are different and nice) for one error. Is there really needed parser error annotation in the time when user has picked the error in output and the error is highlighted by different bgcolor? What is also strange - error underline disapears when the line is highlighted by red bgcolor but the icon stays there. If the icon disapears with the underline the problem of two icons is gone. I don't think that changing icon would be good resolution.
IMHO this requires some UI research spanning compilation and parsing. The editor only provides the infrastructure for annotation attaching here. I don't know what's the most appropriate module for reassigning here. Preliminarily choosing ant and adding java to cc.
No known way to fix this. The Ant module has no way of knowing that there is already a parser error icon there. Re. the apparent change in appearance - in general whenever there is more than one annotation on a line, only one is actively displayed at a time; you can cycle the active annotation by clicking in the margin. Any background annotations display only a dim icon.
I don't agree with WONTFIX resolution. It is simply strange and confusing to show two error annotations for one error in code. First step to fixing it might be the mentioned change of the icon, then parser error would look different than compilation error (which is in fact again wrong because it's still the one same error). I know I can cycle through all annotations but it doesn't have sense to cycle through two annotations for one error.
As you like, but no plans to work on it. Sending to java component since it is Java-specific, though not the fault of the Java background parser as such; rather, the background parser and the Ant error hyperlinker would need to cooperate through some kind of API to avoid duplicate annotations. I am not sure exactly how it would work.
UI issue; code is working as designed.
This is not P3 IMHO.
Sorry, I still think that this is P3, because the UI shows something that is not true in the moment - the gutter shows two errors and code contains only one error.
Effort needed to fix this bug does not match desired effect. To fix this bug we would probably need change annotation API or project dependencies and maybe other things. This bug is wantfix. As far as I know you are the only one who interferes with this behavior.
Sorry, but it's not an argument that I'm the only one who interferes with this behavior. There are thousands of issues reported by one user and such issues are completly valid. IMO implementation problems are not determining if the issue is supposed to be fixed or not. If there is bad design it should be fixed in long term. Reopening the issue and lowering priority, because *there is a bug* that UI shows something that is not true at the moment.
I just tried that in Eclipse and guess what. They show only one annotation in editor, because there is only one error.
Agreed that it is better to have just one annotation. Anyway this is an enhancement request, not a defect and we will not be able to address it in 4.1.
*** This issue has been marked as a duplicate of 22374 ***
Reorganization of java component