JDK-4929871 : spurious ambiguity errors with import
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 5.0
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_8
  • CPU: generic
  • Submitted: 2003-09-29
  • Updated: 2003-11-11
  • Resolved: 2003-11-11
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.
Other
5.0 b28Fixed
Related Reports
Relates :  
JDK-6297388 - JSR 199: compile against a class loader
Relates :  
JDK-4884673 - Can't find class which is in the classpath problem using javac
Description
javac sometimes fails (nondeterministically) complaining that a type name is ambiguous.  One name was typically imported, but the other tends to be a class nested within one that was imported (and which should not be seen).

This is almost certainly a regression caused by changes made as part of the fix for 4792166.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger tiger-beta FIXED IN: tiger-beta INTEGRATED IN: tiger-b28 tiger-beta
14-06-2004
WORK AROUND You can work around the problem by avoiding *-imports for package where the conflicting name is found. Alternately, you can add a named import for the correct one. ###@###.### 2003-10-23
23-10-2003
EVALUATION Correct. ###@###.### 2003-09-29
29-09-2003