Community
Participate
Working Groups
Build ID: M20070212-1330 Steps To Reproduce: 1. Switch malformed javadoc settings to Error 2. Enter an empty javadoc comment, e.g. /** * */ 3. See it not complaining. More information:
Note that this also includes @param tags. As long as the @param exists, Eclipse won't complain about having no description.
(In reply to comment #1) > Note that this also includes @param tags. As long as the @param exists, Eclipse > won't complain about having no description. The missing description issue will be addressed by bug 73352.
Thanks. This bug should probably be marked as a dup then.
(In reply to comment #3) Jason, I think this bug can not be considered as a dup of bug 73352. This one is about not complaining when dealing with empty javadoc, whereas bug 73352 is about missing description in non empty javadoc (the tag is present, but there is no description).
> 2. Enter an empty javadoc comment, e.g. > /** > * > */ > 3. See it not complaining. May be be it's worth wondering whether an empty javadoc should be considered as invalid or not: 1 - did not find anything in the javadoc spec saying that empty javadocs are not allowed or invalid 2 - the javadoc tool won't complain either when encountering empty javadocs tag validation was addressed with bug 73352. This makes me think we could close this bug as invalid.
(In reply to comment #5) performed additional tests / javadoc tool reference search: 1 - still nothing found in the javadoc spec saying that empty javadocs are not allowed or invalid 2 - did not find a test case where the javadoc tool would complain when encountering empty javadocs closing as INVALID. Feel free to reopen in case you find something in the javadoc spec or a test case that causes the javadoc tool to raise an error.
closing as INVALID
Verified for 3.4RC2. The JDT compiler behaves like javadoc tool and it seemed that the real need was more about missing description on @param tag addressed by bug 73352.
*** Bug 201599 has been marked as a duplicate of this bug. ***
