Skip to content

8373909: JSpec and ToolGuide taglets use incorrect relative path#28878

Closed
dansmithcode wants to merge 8 commits intoopenjdk:masterfrom
dansmithcode:8373909
Closed

8373909: JSpec and ToolGuide taglets use incorrect relative path#28878
dansmithcode wants to merge 8 commits intoopenjdk:masterfrom
dansmithcode:8373909

Conversation

@dansmithcode
Copy link

@dansmithcode dansmithcode commented Dec 17, 2025

Fixing the JSpec and ToolGuide taglets so that they produce correct links, no matter what file the tag appears in.

This is a workaround solution, sharing the necessary info via a ThreadLocal public static field in an internal API. See JDK-8373922 for an API enhancement request that would make this possible without relying on internal API.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8373909: JSpec and ToolGuide taglets use incorrect relative path (Bug - P3)(⚠️ The fixVersion in this issue is [26] but the fixVersion in .jcheck/conf is 27, a new backport will be created when this pr is integrated.)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28878/head:pull/28878
$ git checkout pull/28878

Update a local copy of the PR:
$ git checkout pull/28878
$ git pull https://git.openjdk.org/jdk.git pull/28878/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28878

View PR using the GUI difftool:
$ git pr show -t 28878

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28878.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 17, 2025

👋 Welcome back dlsmith! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Dec 17, 2025

@dansmithcode 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:

8373909: JSpec and ToolGuide taglets use incorrect relative path

Reviewed-by: liach, hannesw

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 17 new commits pushed to the master branch:

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot added javadoc javadoc-dev@openjdk.org build build-dev@openjdk.org labels Dec 17, 2025
@openjdk
Copy link

openjdk bot commented Dec 17, 2025

@dansmithcode The following labels will be automatically applied to this pull request:

  • build
  • javadoc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@dansmithcode
Copy link
Author

Planning to integrate this into 27 and create a backport to 26

@openjdk openjdk bot added the rfr Pull request is ready for review label Dec 17, 2025
@dansmithcode
Copy link
Author

dansmithcode commented Dec 17, 2025

The relevant test is jdk/javadoc/doccheck/checks/jdkCheckLinks.java, which is currently problem-listed and will be turned back on via JDK-8370249. It fails before this fix, passes afterwards (when I take it off the problem list).

@mlbridge
Copy link

mlbridge bot commented Dec 17, 2025

Webrevs

private String currentPath() {
try {
Class<?> c = Class.forName("jdk.javadoc.internal.doclets.formats.html.HtmlDocletWriter");
ThreadLocal<?> tl = (ThreadLocal<?>) c.getField("CURRENT_PATH").get(null);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hope the performance overhead of repeated reflective lookup is acceptable... Ideally we should keep the Field in a static final variable.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, fair point (although n is fairly small). Pushed an update that caches the ThreadLocal in a static field.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 17, 2025
@liach
Copy link
Member

liach commented Dec 17, 2025

I checked whether we can make the taglet compile against jdk.javadoc and use the field directly - don't think it's worth the make system hassle.

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Dec 18, 2025
Copy link
Member

@liach liach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 18, 2025
Copy link
Member

@hns hns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@dansmithcode
Copy link
Author

/integrate

@dansmithcode
Copy link
Author

/backport :jdk26

@openjdk
Copy link

openjdk bot commented Dec 18, 2025

Going to push as commit 0b27124.
Since your change was applied there have been 23 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Dec 18, 2025
@openjdk openjdk bot closed this Dec 18, 2025
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Dec 18, 2025
@openjdk openjdk bot removed the rfr Pull request is ready for review label Dec 18, 2025
@openjdk
Copy link

openjdk bot commented Dec 18, 2025

@dansmithcode Pushed as commit 0b27124.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@openjdk
Copy link

openjdk bot commented Dec 18, 2025

@dansmithcode the backport was successfully created on the branch backport-dansmithcode-0b271240-jdk26 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk26, just click the following link:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit 0b271240 from the openjdk/jdk repository.

The commit being backported was authored by Dan Smith on 18 Dec 2025 and was reviewed by Chen Liang and Hannes Wallnöfer.

Thanks!

If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-dansmithcode-0b271240-jdk26:backport-dansmithcode-0b271240-jdk26
$ git checkout backport-dansmithcode-0b271240-jdk26
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-dansmithcode-0b271240-jdk26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build build-dev@openjdk.org integrated Pull request has been integrated javadoc javadoc-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

3 participants