Bugzilla – Full Text Bug Listing
| Summary: | [javadoc] severity level of malformed javadoc comments did not work properly | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Leif Hanack <leif.hanack> | ||||||
| Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | ||||||||
| Version: | 3.2.1 | ||||||||
| Target Milestone: | 3.3 M4 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 54797 [details]
show that to much errors are found
show an example of the wrong detection of malformed javadoc comments. as shown in the preferences dialog, the visibility is set to PUBLIC, therefore default, protected and private should not throw an error.
Missing text in @return cannot be considered as a syntax error (which are always reported whatever the visibility level see bug 77602 comment 1) => I agree we have to hide this warning according to member visibility... Created attachment 54908 [details]
Proposed patch
Released for 3.3 M4 in HEAD stream. Verified for 3.3M4 with I20061212-0010. |
Build ID: M20060921-0945 Steps To Reproduce: 1) create a class with the some method each a different access scope: /** * @return */ private String getSomePrivate() { return "SomePrivate"; } /** * @return */ protected String getSomeProtected() { return "SomeProtected"; } /** * @return */ String getSomeDefault() { return "SomeDefault"; } /** * @return */ String getSomePublic() { return "SomePublic"; } 2) Changing the preferences of Preferences > Java > Compiler > Javadoc > Malformed Javadoc Comments severity level ERROR and visibility to PUBLIC (see screenshot) 3) apply changes 4) even the default, protected and private method javadoc comments are marked as error (see screenshot) More information: using project specific settings/preferences did not change this.