P2
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.
This is almost certainly a regression caused by changes made as part of the fix for 4792166.
- relates to
-
JDK-4884673 Can't find class which is in the classpath problem using javac
-
- Closed
-
-
JDK-6297388 JSR 199: compile against a class loader
-
- Closed
-