Bug 547143 - All Save Actions and Cleanup Tasks that affect style should be available in JDT formatter
Summary: All Save Actions and Cleanup Tasks that affect style should be available in J...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.23   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-09 16:18 EDT by Christopher Tubbs CLA
Modified: 2023-05-15 12:03 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Tubbs CLA 2019-05-09 16:18:49 EDT
Certain Save Actions and Cleanup Tasks that affect code style should also be available in the formatter. This is not the case. The most notable example off the top of my head is the option to strip trailing whitespace characters, which is available as a Save Action, but is not available as a formatting option.

This makes it very difficult to get all the formatting goodness when using the formatter API directly, in such tools as the formatter-maven-plugin, which wrap the formatter, but do not have Save Actions or Cleanup Tasks implemented.
Comment 1 Eclipse Genie CLA 2021-04-29 11:28:26 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.
Comment 2 Eclipse Genie CLA 2023-05-14 12:30:54 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.