-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b154
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8174476 | 10 | Kumar Srinivasan | P3 | Resolved | Fixed | b01 |
The API getDocTreePath(FileObject fileObject) was added earlier, this allowed a way access the parsed document comments in a package.html file.
However, this API does not go far enough, as the user has to maintain a mapping of the package FileObject to the DocTreePath. It will be far more efficient If the API instead took in a PackageElement,and stored that in the synthetic JCCompilationUnit, thus eliminate additional mappings.
However, this API does not go far enough, as the user has to maintain a mapping of the package FileObject to the DocTreePath. It will be far more efficient If the API instead took in a PackageElement,and stored that in the synthetic JCCompilationUnit, thus eliminate additional mappings.
- backported by
-
JDK-8174476 Compiler Tree API's Doctrees.getDocTreePath needs to accept a PackageElement
-
- Resolved
-
- relates to
-
JDK-8157611 field visiblePackages is null for the unnamed module producing NPE when accessed
-
- Closed
-
-
JDK-8173068 ElementUtils getPackageElement does not allow for an unnamed package
-
- Closed
-
-
JDK-8132096 Augment the Compiler Tree API to support the new Simplified Doclet API
-
- Closed
-