Bug 48385 - [DCR] Need Javadoc warning for {@link }
Summary: [DCR] Need Javadoc warning for {@link }
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.0 M7   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 45782
  Show dependency tree
 
Reported: 2003-12-09 21:47 EST by Gary Gregory CLA
Modified: 2004-02-11 07:20 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Gregory CLA 2003-12-09 21:47:52 EST 
Javadoc warnings for bad syntax and references for @see and {@link } tags would
kick booty. 

Right now, I have to run my Ant or Maven scripts to get to see these. Thanks,
eclipse rules.

Version 3.0.m5.
Comment 1 Philipe Mulet CLA 2003-12-10 04:59:57 EST 
@see references are already supported. Nested tags are not yet: {@link}.
Comment 2 Gary Gregory CLA 2003-12-10 17:36:30 EST 
I stand corrected on the @see part, there /is/ a yellow underline squigly under
plarts of my @see lines but there is no warning icon in the left hand vertical bar.
Comment 3 Frederic Fusier CLA 2003-12-11 04:20:53 EST 
Have you saved and built your class? Left warning/error icon only appears when 
build is performed. This is the same behavior than for warning/error displayed 
in Problems view...
Comment 4 Frederic Fusier CLA 2003-12-11 09:12:04 EST 
see also bug 45782
Comment 5 Gary Gregory CLA 2003-12-11 19:31:35 EST 
You are correct once more. I had not saved the file, only edited it. Once saved,
the warning icon appears as expected. This leaves the {@link} (and {@linkplain})
business.
Comment 6 Frederic Fusier CLA 2004-01-13 05:18:07 EST 
Fixed.

Main change is in jdt.internal.compiler.parser.JavadocParser.checkDeprecation
(int,int). When javadoc option is activated we scan all comment characters 
instead of just looking at beginning of line.

When {@link} or {@linplain} is encountered in the line then it's parsed same as 
a see tag. {@inheritDoc} tag are also parsed (see bug 45782).

New error message jdt.core.compiler.IProblem.JavadocInvalidTag has been added 
to display specific error when following invalid syntax is written:
 * An line in javadoc comment {@link String {@link Object}}
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Javadoc: Invalid tag

Test cases added in jdt.core.tests.compiler.regression.JavadocTestMixed.
Comment 7 Frederic Fusier CLA 2004-01-13 05:21:14 EST 
*** Bug 43715 has been marked as a duplicate of this bug. ***
Comment 8 David Audel CLA 2004-02-11 07:20:24 EST 
Verified for 3.0M7