Community
Participate
Working Groups
When javadoc is added to a method, TODO tags should be inserted at appropriate places. Note that when I use Refactor / Change Method Signature to add a parameter to an existing method which allready has javadoc, the new parameter is added to the javadoc. This new parameter in the javadoc *does* get a TODO tag. This difference is inconsistent behaviour. Eclipse 3.2M1
I do not know the internal mechanism which adds javadoc to methods, but Refactor / Extract Method does *not* add a TODO tag, this in contrast to Refactor / Change method signature. These actions should all behave the same when adding javadoc.
You could add the todo tag to the new method comment code template.
What we want to avoid is the fact that TODO tags get scattered all over the place. So we only generate them when we modify code out of the scope of the current action (for example change method signature can be invoked on the calling side of the method and the actual declaration isn't visible in the editor. This is not the case for Add Javadoc comment or extract method. Now that we have Javadoc warnings I am more in favour of having a warning for a missing description that generating TODO tags. I opened a corresponding PR against JDT/Core. Waiting for comments on bug 108798.
As Dirk Baeumer said, warning about empty javadoc tags (bug 73352) should be the proper way of doing this. Koen, what do you think about this now that you have received some feedback about it?
Generating a warning seems fine to me.
Cool! Would it be possible for you to close this bug in that case, since bug 73352 contains the more widely agreed upon solution? I would have done it myself if I had the permissions to do so...
Bug closed in favor of https://bugs.eclipse.org/bugs/show_bug.cgi?id=73352
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.