This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | /** as abbreviation for full javadoc comment | ||
---|---|---|---|
Product: | usersguide | Reporter: | _ tboudreau <tboudreau> |
Component: | Editor | Assignee: | issues@editor <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
_ tboudreau
2001-11-23 13:24:32 UTC
Target milestone -> 3.3.1. Set target milestone to TBD Set target milestone to TBD If you need a multiline comment, see issue 23571, if you need to create a javadoc comment why don't you use the "tools -> correct javadoc", seems to be doing what you're asking for... if that's the case, maybe you can close the issue, if it's the former mark as a duplicate of 23571... if not, well, maybe I misunderstood your problem :-) Changed subcomponent to documentation. Are you sure the documentation subcomponent is correct here? Maybe the Editor team uses it differently, but traditionally we've used the documentation subcomponent to indicate a bug in the javadoc of a module's API, not the editor's support for javadoc. You could also automatically add @param @return .. tags. This would be way faster than using the auto completion dialogue box each time i create a new method and thus would definately improve usability. I've seen that jDeveloper suppports that, I'm not certain with Eclipse... I think we should finally implement this for promoF. Once implemented we should IMHO change the behavior of the Enter pressed at the end of the line inside Javadoc comment - currently it inserts '<indent>*' i.e. /** * typed text *| as the user may want to type '/' to end the comment. After implementation of this enhancement we should start adding an extra space after '*' i.e. /** * typed text * | */ as the closing '*/' was inserted automatically. Mila, I completely agree, this is how other IDEs have it, let's do it this way. *** Issue 35666 has been marked as a duplicate of this issue. *** this is implemented in 6.0 |