JDK-6794582 : javadoc should read files using a FileManager
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2009-01-16
  • Updated: 2014-06-06
  • Resolved: 2011-07-15
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 7 Other
7 b46Fixed OpenJDK6Fixed
Related Reports
Duplicate :  
JDK-6591404 - Need to investigate and cleanup javadoc code for using internal javac classes
Relates :  
JDK-4789256 - Enable javadoc to process source files in .zip or .jar file
Relates :  
JDK-8046096 - JEP 106: Add Javadoc to javax.tools
Relates :  
JDK-6493690 - javadoc should have a javax.tools.Tool service provider installed in tools.jar
Relates :  
JDK-6794587 - javadoc should write files using a FileManager
Description
javadoc should read files using a FileManager, instead of directly using the File API.
Comments
EVALUATION Yes. For the most part, this is reasonably easy. There is only one problem case, in ClassDocImpl, where javadoc currently looks for the package doc in package doc in the same directory as the class' source file. The right way to do this in JSR 199 is to look for the package file on the source path. The old way is problematic for a general file manager. the fix is to try looking on the source path, and if not found, and if its a standard file manager, to roll over to the old behavior using direct access to the file system.
16-01-2009