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 37358 - Ant hyperlinking should better handle javac's column number info
Summary: Ant hyperlinking should better handle javac's column number info
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
Depends on: 42525
  Show dependency tree
Reported: 2003-11-20 00:23 UTC by Jesse Glick
Modified: 2005-12-20 15:46 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2003-11-20 00:23:29 UTC
Jikes is nice in its +E output since it gives you
start and end line and column numbers for the
error - precisely what you need to make a good

Javac is more annoying. It will tell you e.g.:

/some/ not a statement

What you wanted it to print was e.g.

/some/ not a statement

i.e. include the column number in the action error
message. (Ideally end point too, but forget about
that for now.)

Ant's current parsing - in AntOutputParser, used
from AntOutputStream - cannot get the column
number here. But if it did a two-line lookahead
search, it could check if there is an error
message followed by some line to be ignored
followed by a line consisting of some number of
spaces and ending with a '^'. In this case, it
should think of a column number according to the
number of spaces given, and make the hyperlink

This would make F12 from javac output slightly
more pleasant, and would probably be an adequate
substitute for term's compiler error region detection.
Comment 1 Jesse Glick 2004-06-09 01:18:00 UTC
Implemented in ant_loggers_42525 branch, in the standard logger.
Doesn't use lookahead; just retroactively stores the column number if
it encounters a '^' line, so that F12 jumps to the right place.
Comment 2 Jesse Glick 2004-06-12 02:47:04 UTC
Comment 3 Marian Mirilovic 2005-12-20 15:46:24 UTC
This issue was solved long time ago. Because nobody has reopened it neither
added comments, we are verifying/closing it now. 
If you are still able to reproduce the problem, please reopen. Thanks in advance.