Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365367

Summary:	Javadoc compiler check for malformed javadoc is checking more than javadoc comments
Product:	[Eclipse Project] JDT	Reporter:	Daniel Holmes <dholmes>
Component:	Core	Assignee:	Stephan Herrmann <stephan.herrmann>
Status:	VERIFIED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	manoj.palat, satyam.kandula, stephan.herrmann
Version:	3.8
Target Milestone:	4.14 M1
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Daniel Holmes

2011-12-01 17:42:14 EST

Build Identifier: 20100917-0705

I'm trying to just enable checking to solve problems of bad @param and @return tags in my javadoc.  But turning this on is flagging a number of other issues on actual annotations in my code (incorrected even) that I would not expect.  By its name, it seems this checking should be limited to tagging purely within actual javadoc comments.  How can I get this behavior?

Reproducible: Always

Comment 1 Satyam Kandula

2011-12-01 23:58:04 EST

Annotations in the code will always be resolved by the compiler. Hence, I don't understand what you mean. Can you give a test case?

Comment 2 Eclipse Genie

2019-09-30 11:59:33 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Stephan Herrmann

2019-09-30 15:47:27 EDT

No actionable information provided.

Comment 4 Manoj N Palat

2019-10-09 10:49:57 EDT

Verified for Eclipse Version: 2019-12 (4.14) M1 with  Build id: I20191008-1800