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.
| Summary: |
Ant hyperlinking should better handle javac's column number info |
| Product: |
projects
|
Reporter: |
Jesse Glick <jglick> |
| Component: |
Ant | Assignee: |
Jesse Glick <jglick> |
| Status: |
VERIFIED
FIXED
|
|
|
| Severity: |
blocker
|
CC: |
tboudreau
|
| Priority: |
P3
|
|
|
| Version: |
3.x | |
|
| Hardware: |
All | |
|
| OS: |
All | |
|
|
Issue Type:
|
ENHANCEMENT
|
Exception Reporter:
|
|
|---|
| Bug Depends on: |
42525
|
|
|
| Bug Blocks: |
|
|
|
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 hyperlink. Javac is more annoying. It will tell you e.g.: /some/File.java:99: not a statement method();x ^ What you wanted it to print was e.g. /some/File.java:99:18: not a statement method();x ^ 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 accordingly. This would make F12 from javac output slightly more pleasant, and would probably be an adequate substitute for term's compiler error region detection.