Now that jdk-12+14 is out, using the jdk12 javadoc command to generate docs
linking to jdk11 external docs works well!
Doug, you will probably need to update your jdk12 to jdk-12+14 and
regenerate jsr166 docs.
On Mon, Oct 1, 2018 at 3:40 PM, Martin Buchholz wrote:
> I am a lot happier after di
Martin,
Finding and fixing broken links continues to be a priority for us as well.
Regrettably, there is a lot of technical debt in this area, and
sometimes the noise of the "minor" errors drown out the signal of the
more significant errors.
-- Jon
On 10/01/2018 03:40 PM, Martin Buchholz wro
I am a lot happier after discovering Priya's fix in progress!
(but after all these years my top priority for java documentation remains
ensuring that the process makes broken links impossible, like a
compile-time error in the java source)
On Mon, Oct 1, 2018 at 3:06 PM, Michel Trudeau
wrote:
>
This appear to be a dup of [1], we will verify and make sure it is before
closing the issue as such. Also, we will evaluate the backport.
-Michel
[1] https://bugs.openjdk.java.net/browse/JDK-8205593
On Sep 30, 2018, at 9:56 PM, Martin Buchholz wrote:
I found
https://bugs.openjdk.java.net/br
I found
https://bugs.openjdk.java.net/browse/JDK-8211194
javadoc -link doesn't take module path into consideration
and raised the priority of that bug.
On Wed, Sep 26, 2018 at 6:47 PM, Martin Buchholz
wrote:
> I was trying to migrate to using the shiny
> https://docs.oracle.com/en/java/javase/1
I was trying to migrate to using the shiny
https://docs.oracle.com/en/java/javase/11/
for all my documentation needs and ran into some troubles:
Every year I complain about no one checking for dead links in the docs.
Running a dead-link checker before a major release should be easy-peasy.
E.g. in
