On Wed, 13 Dec 2023 10:44:43 GMT, Hannes Wallnöfer <hann...@openjdk.org> wrote:
>> Should this issue have a CSR for the behavioral change? > >> Should this issue have a CSR for the behavioral change? > > My understanding of the issue is that the lookup of explicit-class member > references in enclosing classes was an unintended consequence of doing the > same for classless references from within nested classes. So I consider this > a bug fix, not a feature change (even though it unfortunately changes javadoc > to become stricter in what it accepts). > > Actually, the feature of extending member reference lookup to enclosing > classes is not specified in the taglet spec, which only says this: > >> When the reference is to a member of the same class as that containing the >> documentation comment, all parts of the reference up to and including the # >> may be omitted, although the '#' may be retained for clarity. > > This could be extended to include enclosing classes, but this is existing > behaviour, not changed by this issue. > @hns would you be able to create a linked bug to track that lookup order > issue? I filed an issue for it here: https://bugs.openjdk.org/browse/JDK-8324320 Ping: since most of the discussion in this PR was off-topic, could somebody please review the actual change? ------------- PR Comment: https://git.openjdk.org/jdk/pull/17069#issuecomment-1904218001
