Use latest Java toolchain and simplify Javadoc generation now that the javadoc
tool can properly link to older docs
#13
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.
Use latest Java toolchain and simplify Javadoc generation now that the
javadoc
tool can properly link to older docs with the following tickets fully complete:The only remaining issue is Gradle's own Javadocs, in that
Project.html#getName--
),javadoc
implementation into generating them in HTML5 format (e.g.Project.html#getName()
),I will try to ask the Gradle maintainers to fix this before I merge this PR. The possible solutions:
javadoc
and generate modern HTML5, which would also fix their links to JDK classeselement-list
and only keeppackage-list
if the docs have to be in HTML4 formatelement-list
file being there is what misleads the new, smartjavadoc
implementation – if there is anelement-list
, then it callsreadElementList(in, urlpath, false, 0, false)
, otherwise it does the same with atrue
as the last parameter (isOldFormDoc
)