Bugzilla – Full Text Bug Listing
| Summary: | [formatting] Should not apply Javadoc formatter setting to traditional comments | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Peter Smith <poida.smith> |
| Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
| Status: | VERIFIED DUPLICATE | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | gunnar, n.a.edgar |
| Version: | 3.1 | ||
| Target Milestone: | 3.3 M5 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Reproducible in I2050315-1100. The problem is that we honor the "Blank line before Javadoc tags" for traditional comments as well. You could check the "Clear blank lines in comments" option for now. Ownership changed. Using 3.3M5, javadoc comments, block comments and line comments can be formatted separately. So disabling formatting for block comment should fix this issue. Closing as dup of bug 49412. *** This bug has been marked as a duplicate of bug 49412 *** *** Bug 115913 has been marked as a duplicate of this bug. *** Verified for 3.3M5. |
The non javadoc comments that are generated when (eg) overriding a method are formatted like this: /* (non-Javadoc) * @see java.lang.Object#toString() */ public String toString() { return super.toString(); } This is a nice and compact comment. The java code formatter that comes with the JDT will always reformat this to be like this: /* * (non-Javadoc) * * @see java.lang.Object#toString() */ public String toString() { return super.toString(); } This is much less compact and there doesn't appear to be a setting so the formatting is like the first one.