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.

Bug 51199 - Double error annotation in editor (Ant hyperlinks + Java background parser)
Summary: Double error annotation in editor (Ant hyperlinks + Java background parser)
Status: RESOLVED DUPLICATE of bug 22374
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-05 13:14 UTC by Milan Kubec
Modified: 2007-09-26 09:14 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kubec 2004-11-05 13:14:01 UTC
[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.
Comment 1 Martin Roskanin 2004-11-05 14:00:04 UTC
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.
Comment 2 Milan Kubec 2004-11-05 14:16:05 UTC
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.
Comment 3 Miloslav Metelka 2004-12-01 13:12:55 UTC
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.
Comment 4 Jesse Glick 2004-12-01 16:47:26 UTC
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.
Comment 5 Milan Kubec 2004-12-02 08:17:03 UTC
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.
Comment 6 Jesse Glick 2004-12-02 16:29:35 UTC
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.
Comment 7 Jesse Glick 2004-12-02 16:30:27 UTC
UI issue; code is working as designed.
Comment 8 Jan Becicka 2005-01-14 15:40:00 UTC
This is not P3 IMHO.
Comment 9 Milan Kubec 2005-01-14 15:45:25 UTC
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.
Comment 10 Jan Becicka 2005-02-11 08:28:20 UTC
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.
Comment 11 Milan Kubec 2005-02-11 10:16:20 UTC
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.
Comment 12 Milan Kubec 2005-02-11 10:26:02 UTC
I just tried that in Eclipse and guess what. They show only one
annotation in editor, because there is only one error.
Comment 13 Martin Matula 2005-02-11 10:56:34 UTC
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.
Comment 14 Jan Becicka 2005-10-12 15:58:15 UTC

*** This issue has been marked as a duplicate of 22374 ***
Comment 15 Quality Engineering 2007-09-20 12:50:53 UTC
Reorganization of java component