JDK-6413633 : JSR 199: file manager requirements
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-04-14
  • Updated: 2010-04-02
  • Resolved: 2006-05-13
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 6
6 b85Fixed
Related Reports
Relates :  
JDK-6409829 - JSR 199: enforce the use of valid package and class names in get{Java,}FileFor{Input,Output}
Description
###@###.### writes:

- is it allowed to use any JavaFileManager for the JavaCompilerTool, or 
is it possible that a JavaCompilerTool might accept only its own default 
standard FileManager ?
- what does the JavaCompilerTool if used with the direct run method ?
Comments
SUGGESTED FIX 4 14:11:30.300511676 -0700 +++ JavaCompilerTool.java 2006-04-24 14:11:10.229341373 -0700 @@ -29,6 +29,12 @@ * standard file manager can be obtained by calling {@linkplain * #getStandardFileManager getStandardFileManager}. * + * <p>A compiler tool must function with any file manager as long as + * any additional requirements as detailed in the methods below are + * met. If no file manager is provided, the compiler tool will use a + * standard file manager as the one returned by {@linkplain + * #getStandardFileManager}. + * * <p>An instance implementing this interface must conform to the Java * Language Specification and generate class files conforming to the * Java Virtual Machine specification. The versions of these
24-04-2006
EVALUATION The documentation should be clarified.
21-04-2006