[JENKINS-68761] javadoc.jenkins.io navigation issues with Java 11 generated javadoc #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
See JENKINS-68761.
Steps to reproduce
Generate the Javadoc site, then attempt to search for a class in the Jenkins core or Winstone Javadocs (both compiled with Java 11).
Expected results
The class is found in the search results, and clicking the link takes you to the class's Javadoc.
Actual results
The class is found in the search results, but clicking on the link takes you to a nonexistent page.
Evaluation
This is JDK-8215291.
Solution
Pending the merge, release, and subsequent adoption of openjdk/jdk11u-dev#1157, work around the problem by munging the file ourselves.
Testing done
Built the Javadocs locally and started a web server against the generated site. Reproduced the problem as described above, and could no longer reproduce the problem after these changes.