-
Bug
-
Resolution: Fixed
-
P2
-
6
-
b85
-
generic
-
generic
-
Verified
package-info is not a legal class name. The specification should be
changed to allow these kind of class names.
- duplicates
-
JDK-6415881 JSR 199: DefaultFileManager.getFileForInput does not validate input
- Closed
- relates to
-
JDK-6411073 JSR 199: questions not answered by the specification
- Resolved
-
JDK-6411312 JSR 199: ForwardingFileManager should be generic, by analogy with ForwardingFileObject
- Resolved
-
JDK-6412308 JSR 199: javax.tools.JavaFileManager.getFileForOutput: spec is the same as for getFileForInput
- Resolved
-
JDK-6413633 JSR 199: file manager requirements
- Resolved
-
JDK-6410174 JVMS should be clarified regarding internal form of class name
- Resolved
-
JDK-6417282 JSR 199: default is not system
- Resolved
-
JDK-6392177 JSR269: Support creating package-info.java files
- Closed
-
JDK-6411310 JSR 199: FileObject should support user-friendly names via getName()
- Closed
-
JDK-6415780 JSR 199: javax.tools.JavaFileManager.getClassLoader always fails
- Closed
-
JDK-6418694 JSR 199: JavaFileManager.hasLocation(Location)
- Closed
-
JDK-6420409 JSR 199: StandardFileManager: cannot set CLASS_PATH location
- Closed
-
JDK-6420464 JSR 199: JavaFileObject.isNameCompatible throws unspecified exception (IllegalArgumentException)
- Closed
-
CODETOOLS-6419713 some regression tests need /othervm
- Closed
-
JDK-6410643 JSR 199: The method JavaCompilerTool.run fails to handle null arguments
- Closed
-
JDK-6412656 JSR 199: pass annotation processor instances to compiler
- Closed