-
Bug
-
Resolution: Fixed
-
P3
-
17
-
b28
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8269196 | 18 | Jan Lahoda | P3 | Resolved | Fixed | b03 |
JDK-8270617 | 17.0.1 | Jan Lahoda | P3 | Resolved | Fixed | b03 |
The following specification
https://docs.oracle.com/en/java/javase/16/docs/api/java.compiler/javax/tools/StandardJavaFileManager.html#setLocationFromPaths(javax.tools.JavaFileManager.Location,java.util.Collection)
says:
Implementation Requirements:
The default implementation converts each path to a file and calls getJavaObjectsFromFiles
Actually OpenJDK implementation calls `setLocation()` with an iterable over given paths lazily converted to files.
https://docs.oracle.com/en/java/javase/16/docs/api/java.compiler/javax/tools/StandardJavaFileManager.html#setLocationFromPaths(javax.tools.JavaFileManager.Location,java.util.Collection)
says:
Implementation Requirements:
The default implementation converts each path to a file and calls getJavaObjectsFromFiles
Actually OpenJDK implementation calls `setLocation()` with an iterable over given paths lazily converted to files.
- backported by
-
JDK-8269196 StandardJavaFileManager::setLocationFromPaths() spec contains an error
-
- Resolved
-
-
JDK-8270617 StandardJavaFileManager::setLocationFromPaths() spec contains an error
-
- Resolved
-
- is cloned by
-
JDK-8266591 StandardJavaFileManager::getJavaFileObjectsFromPaths() methods contain a typo in their spec
-
- Resolved
-
(1 links to)