rgoossens / workspacemechanic

Automatically exported from code.google.com/p/workspacemechanic
0 stars 0 forks source link

Java Source Formatter is Applied but not really #122

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create an epf with your java source formatter changes
2. Create a new workspace and apply the changes when prompted by workspace 
mechanic
3. Format the a java file. 

What is the expected output? What do you see instead?
For me it is not applying the imported formatter. When I look in preferences 
the formatter is selected, but it is not using the settings. 

To work around this, I select a different formatter and apply the preference 
change. Then I change it back to the formatter that workspace mechanic imported 
and apply the change. After I do that it will use the formatter correctly.

What version of the product are you using? On what operating system?
Kepler
Windows 8.1
Workspace Mechanic 0.4.0

Please provide any additional information below.

Original issue reported on code.google.com by jdavis4...@gmail.com on 23 Oct 2014 at 3:30

GoogleCodeExporter commented 8 years ago
I can confirm that.
Have the same issues here:
Eclipse Juno and Kepler
Windows 7
Workspace Mechanic 0.3.4 (first version I used) and 0.4.0

Original comment by rs.ricos...@googlemail.com on 21 Nov 2014 at 7:36

GoogleCodeExporter commented 8 years ago
I think it is related to #22.

The formatter profile is modified and set by Mechanic, but Eclipse will 
actually apply the settings only on changing them editing the profile or 
switching between them directly from the preferences page.

To verify this, start recording changes, switch to a different profile, then 
stop the recording: you will see many properties changed, not (only) the 
profile.

To have the things working, a method should be find to export a whole 
formatting profile as list of actual formatting properties.

Original comment by alessio....@gmail.com on 14 Jan 2015 at 3:30