Description Erik Hilsdale 2012-03-30 13:03:52 EDT

Build Identifier: Version: 3.7.2 Build id: M20120208-0800

In Issue 371420 , Eclipse's javadoc handling was broken in order to make it bug compatible with javadoc.exe by reporting that 

  import package.TopLevelType;
  ...
  {@link TopLevelType.NestedType}

is ill-formed javadoc.

This is an enhancement request to allow users to determine whether they want bug-compatibility or spec-compatibility.

Rationale:

Much of the code I work with is not passed through javadoc.exe -- the javadoc
is primarily viewd via the internal-to-eclipse javadoc viewing tools, and
{@link} is valuable as instructions for F3 navigation.

The current situation only allows me four options when I want to {@link ...} to
nested types (or members of nested types)

(a) ignore the warning.  This makes the problems pane less useful to me as
there are tonnes of false positives.

(b) use the "doesn't contain" filter on the problems pane to suppress these. 
Unfortunately, I only get one filter, and I sometimes need that to suppress
deprecated warnings.

(c) don't validate tag arguments.  This leads to javadoc rot.

(d) fully qualify all such references.  This is weird, hard to explain to my
code reviewers, and not very readable.


Reproducible: Always

Steps to Reproduce:
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=371420