JDK-6384376 : JSR 199: JavaFileManager: need constants for standard locations
- Type: Bug
- Component: tools
- Sub-Component: javac
- Affected Version: 6
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2006-02-10
- Updated: 2010-05-11
- Resolved: 2006-03-17
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.
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 |
|---|
6Resolved  |
Related Reports
|
Duplicate :
|
Description
JavaFileManager uses a String argument to determine the directory in which to create files identified by what are effectively relative path names. Currently the set of acceptable string values is undefined. We should define the current set of locations needed by the tools, and provide string constants for optional cleint use. Lack of the constants is setting us up for potential problems later.
Comments
|