8373922: Enhance Taglet API to support relative URLs#30120
8373922: Enhance Taglet API to support relative URLs#30120hns wants to merge 9 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back hannesw! A progress list of the required criteria for merging this PR into |
|
@hns This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 12 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Webrevs
|
|
Can we remove the hack used by JSpec taglet as a POC of this new API? Or do you plan to do in a later RFE? |
|
@liach I've filed a separate issue JDK-8379520 for the Taglet cleanup, but I'm adding the changes to this PR as I think it's good to see the new API in use. I can move it to a separate PR if necessary. |
|
/issue add JDK-8379520 |
|
@hns |
|
@hns |
|
@hns This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a |
|
@hns this pull request can not be integrated into git checkout JDK-8373922
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
/template append |
|
@hns The pull request template has been appended to the pull request body |
|
@liach could you please re-approve this PR? |
|
Thanks! /integrate |
|
Going to push as commit 35ad47b.
Your commit was automatically rebased without conflicts. |
Please review an enhancement that adds a new default
toStringmethod to thejdk.javadoc.doclet.Tagletinterface which receives the path to the documentation root directory as additional argument of typejava.net.URI. (The initial version of this PR usedjava.nio.file.Pathwhich was of course a blunder as that class uses a platform-dependent separator.)This makes it possible to create correct relative URLs when a tag is rendered outside of its element's resource (such as in a summary page), which was previously impossible using the public Taglet API. It also makes it easier to build relative URLs in the common case where a tag is rendered in its element's normal location.
I also added the changes for JDK-8379520 to make use of the new API in JDK build Taglets to this PR. The changes to the
JSpecandToolGuidetaglets consist in undoing the changes from JDK-8373909 and replacing it with the new functionality.For
SealedGraphit's a bit more involved, because in order to be able to use thepathToRootURI I had to change the naming of .svg files for nested classes to not use subdirectories for enclosing classes so that these files use the same directory as all the other files from that package.Progress
Issues
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/30120/head:pull/30120$ git checkout pull/30120Update a local copy of the PR:
$ git checkout pull/30120$ git pull https://git.openjdk.org/jdk.git pull/30120/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 30120View PR using the GUI difftool:
$ git pr show -t 30120Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/30120.diff
Using Webrev
Link to Webrev Comment