8248001: javadoc generates invalid HTML pages whose ftp:// links are broken
I would like to backport 8248001: javadoc generates invalid HTML pages whose ftp:// links are broken. There are minor differences regarding DocRoot, but otherwise this is a clean backport.
Progress
- [x] Change must be properly reviewed (1 review required, with at least 1 Reviewer)
- [x] Change must not contain extraneous whitespace
- [x] Commit message must refer to an issue
- [x] JDK-8248001 needs maintainer approval
Issue
- JDK-8248001: javadoc generates invalid HTML pages whose ftp:// links are broken (Bug - P4 - Approved)
Reviewers
- Paul Hohensee (@phohensee - Reviewer)
Reviewing
Using git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/420/head:pull/420
$ git checkout pull/420
Update a local copy of the PR:
$ git checkout pull/420
$ git pull https://git.openjdk.org/jdk8u-dev.git pull/420/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 420
View PR using the GUI difftool:
$ git pr show -t 420
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/420.diff
Using Webrev
:wave: Welcome back ktakakuri! 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.
This backport pull request has now been updated with issue from the original commit.
@ktakakuri 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 add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
@ktakakuri This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.
/open
@ktakakuri This pull request is now open
❗ This change is not yet ready to be integrated. See the Progress checklist in the description for automated requirements.
Could anyone review this backport please? This is a simple fix, almost a clean backport.
@ktakakuri 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 add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
Can someone please review this backport?
⚠️ @ktakakuri This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.
/approval request There are minor differences regarding DocRoot, but otherwise this is a clean backport. There is no risk, because the logic around the changes and the cause of the problem is the same as in jdk18. Testing: test/langtools on Windows x86_64
@ktakakuri 8248001: The approval request has been created successfully.
@ktakakuri 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 add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
This pull request is pending approval of the Fix Request. I comment to not close.
@ktakakuri 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 add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
This pull request is pending approval of the Fix Request. I comment to not close.
@ktakakuri 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 add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
This pull request is pending approval of the Fix Request. I comment to not close.