Bug 52420 - [formatting] Task tags (TODO) in comments should not be formatted.
Summary: [formatting] Task tags (TODO) in comments should not be formatted.
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-02-18 15:50 EST by Adalbert Homa CLA
Modified: 2019-08-27 18:14 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adalbert Homa CLA 2004-02-18 15:50:35 EST
Formatting javadoc comments, the TODO and other task tags got formatted away.
Example:
    /**
     * Test here a nice long comment. Just an example nothing more. Long
     * comment. Now here comes.
     * TODO: Todo should stay on the same line.
     *  
     */
    public void docTest() {

    }
Formatting this will be:
    /**
     * Test here a nice long comment. Just an example nothing more. Long
     * comment. Now here comes. TODO: Todo should stay on the same line.
     *  
     */
    public void docTest() {

    }

This defeats the purpose of the task tags.
Comment 1 Dani Megert CLA 2004-02-20 04:49:53 EST
see also bug 50896
Comment 2 Stefan Matthias Aust CLA 2004-03-23 04:18:07 EST
In addition please do not wrap lines that start with a TODO, XXX, or FIXME (or
whatever is configured in the preferences) marker because otherwise the tasks
view cannot display the complete description.

As an alternative, make the compiler smarter so that 

/*
 * TODO add support for multi-line
 *      todo marker to the compiler
 * TODO rethink this idea
 */

would work as expected (hopefully bugzilla will not reformat this :)
Comment 3 Dani Megert CLA 2005-10-10 12:09:46 EDT
Ownership changed.
Comment 4 Frederic Fusier CLA 2008-08-18 08:06:27 EDT
Ownership has changed for the formatter, but I surely will not have enough time to fix your bug during the 3.5 development process, hence set its priority to P5.
Please provide a patch if you definitely need the bug to be fixed in this version and I'll have a look at it...
TIA
Comment 5 Eclipse Genie CLA 2019-08-27 18:14:21 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.