JDK-6833594 : changes internal Paths API to allow each path entry to have an associated Set
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 7
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2009-04-23
  • Updated: 2024-04-12
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-6832154 - refactor Paths to be just a utility class for JavacFileManager
Description
Currently, all Path objects are agnostic as to their contents, leading (for example) to complicated code in ClassReader.fillInPackage to process combinations of paths for different content.

Allowing Path objects to be created that allow each entry on the path to provide a hint as to its contents would simplify code elsewhere in the compiler.
Comments
EVALUATION Yes. The basic change is to change Paths.Path from a LinkedHashSet<File> to LinkedHashSet<PathEntry> where PathEntry is a new class containing {File file; Set<JavaFileObject.Kind> kinds}. Once you add PathEntry, it provides an obvious way to clean up canonical file handling, simplify the impl of Path itself, and the additional HashSet<File> canonicalValues.
23-04-2009