JDK-6733837 : Recent work on javac diagnostic affected javac output
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,linux
  • CPU: generic,unknown,x86
  • Submitted: 2008-08-05
  • Updated: 2011-05-18
  • Resolved: 2011-05-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b35Fixed
Related Reports
Duplicate :  
JDK-6740348 - javac crashes when a variable is not declared
Duplicate :  
JDK-6737242 - javac crash with java.lang.StringIndexOutOfBoundsException: String index out of range: 71
Relates :  
JDK-6724071 - refactor Log into a front end and back end
Relates :  
JDK-6720185 - DiagnosticFormatter refactoring
Description
It seems that recent work in javac diagnostic system introduced two little regressions problems:

1) DiagnosticSource refactoring introduced some problems wrt tab characters so that sometimes javac reports a wrong column position when printing a diagnostic

2) When a diagnostic is printed, the source basename (instead of the fullname) of the file the diagnostic refers to is printed. This regression is due to the recent refactoring of diagnostic formatters.
Comments
SUGGESTED FIX A webrev of this change is available at: http://sa.sfbay.sun.com/projects/langtools_data/7/6733837.2
22-08-2008
EVALUATION Will fix for b32
05-08-2008