[jdk19] RFR: 8287379: Using @inheritDoc in an inapplicable context shouldn't crash javadoc [v5]

Pavel Rappo prappo at openjdk.org
Mon Jul 11 15:20:52 UTC 2022


On Mon, 11 Jul 2022 15:01:42 GMT, Jonathan Gibbons <jjg at openjdk.org> wrote:

> 
> That's not the right question. The question is, how can we best replace the functionality of those tests. It's the relative link that's important, not the location. Since the comment containing the relative link can no longer be placed on a top level declaration, they should be moved to a declaration where they are legal, such as on a method.

Hm... While I understand what you are saying, I also think that we already have tests that exercise relative links on methods. Those tests are located in that same directory, no? Here, test/langtools/jdk/javadoc/doclet/testRelativeLinks/pkg/C.java:


public class C {

    /**
     * Here is a relative link in a field:\u0130
     * <a href="relative-field-link.html">relative field link</a>.
     */
    public C field = null;

    /**
     * Here are two relative links in a method:
     * <a href="relative-method-link.html">relative method link</a>,
     * <a href="#method-fragment">fragment method link</a>.
     */
    public C method() { return null;}

    /**
     * Here is a relative link in a method:
     * <a
     * href="relative-multi-line-link.html">relative-multi-line-link</a>.
     *
     * <a id="method-fragment">Method fragment</a>.
     */
    public C multipleLineTest() { return null;}

-------------

PR: https://git.openjdk.org/jdk19/pull/54


More information about the javadoc-dev mailing list