Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359378 - Make compiler settings for JavaDoc project specific
Summary: Make compiler settings for JavaDoc project specific
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.5 M3   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-29 05:27 EDT by Rüdiger Herrmann CLA
Modified: 2011-09-30 05:11 EDT (History)
0 users

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 Rüdiger Herrmann CLA 2011-09-29 05:27:13 EDT 
We crrently do not use project specific compiler setings to check JavaDoc. The default workspace settings are set to ignore most problems. To know and/or improve the quality of our JavaDoc we should make the settings project specific and let the compiler check JavaDoc.
Comment 1 Rüdiger Herrmann CLA 2011-09-30 05:11:17 EDT 
Enabled project-specific JavaDoc settings for org.eclipse.rap.rwt and rwt.osgi. The JavaDoc verifier now shows warnings for malformed JavaDoc comments. 
All existing JavaDoc problems were resolved except for one group of warnings: the JavaDoc verifier complains about unresolved references even though the reference is embedded in HTML comments (<!-- -->). 

I opened bug 359533 against JDT as I think text inside HTML comments should be ignored.