Bug 88570 - [formatting] Should not apply Javadoc formatter setting to traditional comments
Summary: [formatting] Should not apply Javadoc formatter setting to traditional comments
Status: VERIFIED DUPLICATE of bug 49412
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: 3.3 M5   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 115913 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-19 12:47 EST by Peter Smith CLA
Modified: 2007-02-09 08:19 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Smith CLA 2005-03-19 12:47:16 EST
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.
Comment 1 Dani Megert CLA 2005-03-21 05:17:32 EST
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.
Comment 2 Dani Megert CLA 2005-10-10 12:08:58 EDT
Ownership changed.
Comment 3 Olivier Thomann CLA 2007-02-08 10:41:29 EST
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 ***
Comment 4 Olivier Thomann CLA 2007-02-08 11:17:45 EST
*** Bug 115913 has been marked as a duplicate of this bug. ***
Comment 5 Olivier Thomann CLA 2007-02-09 08:19:16 EST
Verified for 3.3M5.