Summary: | [formatter] Bad formatting for @see in non-javadoc method comments | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jared Burns <jared_burns> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | VERIFIED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert, Olivier_Thomann, srikanth_sankaran |
Version: | 3.4.2 | ||
Target Milestone: | 3.6 M5 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Jared Burns
2010-01-15 14:12:15 EST
>First, that the space was removed between the @see >and the start of the package name. I cannot reproduce this using I20100112-0800. >And second, that the line was wrapped at >all. That's expected since traditional comment has no semantics and hence breaks things on word boundaries. Moving to JDT Core for final comment. (In reply to comment #1) > >First, that the space was removed between the @see > >and the start of the package name. > I cannot reproduce this using I20100112-0800. > This issue was fixed just after 3.6M4 (see duplicate bug 297546) > >And second, that the line was wrapped at > >all. > That's expected since traditional comment has no semantics and hence breaks > things on word boundaries. > Agreed, that's the expected behavior for block comments. The reference is not resolved and is just considered as text here. That's why the formatter is allowed to break it to preserve the 'Maximum line width' constraint... *** This bug has been marked as a duplicate of bug 297546 *** Verified for 3.6M6 using build I20100305-1011 |