Community
Participate
Working Groups
Created attachment 286076 [details] screenshot global preferences save actions Global preferences does not work to disable the Java formatter to run upon Save. The "Perform the selected actions on save" checkbox is not selected but that does not disable the formatter to format upon Save the java file. Steps to reproduce are: Open eclipse. Select Windows men > Preferences > Java > Editor > Save actions Ensure that the "Perform the selected actions on save" checkbox is not selected. Apply and Close I did not set the project settings related to this. I read that there are project properties as well. Why? I dont feel like i need to. I see that there is also another bug 477478 that has status RESOLVED WONTFIX Really? Why dont you fix this?
I just read that bug 477478 is about other aspect. So, please disregard my reference to that bug 477478
oh my god ... so i found out the project level save actions has all options enabled including the trigger formatter for all lines before save the java file by default. does not it seem to you that the defaults for the project to be the same as the global save actions ???? attaching the screen now.
Created attachment 286077 [details] project level save actions screnshot
When I test this on a new project, by default a new project does not have project specific save actions enabled. Also, the grayed out options are all set to the same state as the global save actions so that when I enable the project specific settings, I start with the same behavior as global and can modify it. So it looks like you accidentally enabled the project specific save actions to something you don't want. Can you please confirm so we can close the bug report, or if you still see some undesired behavior, provide the steps to reproduce?
When I change the global save actions, then the project specific save actions (if enabled) don't change - that's a valid behavior.
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.
