google-code-export / uimafit

Automatically exported from code.google.com/p/uimafit
2 stars 1 forks source link

add formatter export to subversion and instructions on how to use it #53

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I am a bit confused about Eclipse's project-specific formatting configuration.  
When I updated the formatting configuration to the settings we agreed on 
(assuming I did this right) a user.prefs file in the .settings folder was 
modified and currently consists of lots of formatting-related settings.  I 
thought that checking this in would be enough to change the project settings 
for formatting - but it doesn't seem to be.  I just ran into this with a 
cleartk project.  I had someone else update their local files after I had 
enabled project-specific formatting settings and then checked in the 
differences to the .settings folder.  When he updated his code it had no effect 
on his default formatting configurations.  Poking around a bit I have noticed 
that other projects give instructions on how to import a formatting settings 
xml file generated by the "export" option in the project-specific formatting 
settings wizard.  Anyways, I am concerned that formatting settings are not 
being handled correctly.  Any insight to clear up my confusion is appreciated.  

Original issue reported on code.google.com by pvogren@gmail.com on 15 Jan 2011 at 12:12

GoogleCodeExporter commented 9 years ago
I would have thought that since those settings are saved in the .settings 
folder, they should properly transfer to other workspaces upon checkout/update 
- for that project only, but not for the default settings. It may be an issue 
of using different versions of Eclipse. 

In general I would prefer not to save the Eclipse metadata in the project at 
all (.project, .classpath, .settings) and rely on people setting up stuff 
themselves. There is an Eclipse plugin for Maven which could be used to 
generate Eclipse settings files, but last time I looked at that, it m2eclipse 
did not support that. At the time i wanted m2eclipse to add specific project 
natures to the .project file upon import.

Original comment by richard.eckart on 15 Jan 2011 at 9:53

GoogleCodeExporter commented 9 years ago
I'm definitely currently seeing that my uimafit project now has "Enable project 
specific settings" checked and "Unmanaged profile 'uimaFIT style'" selected 
under Java Code Style => Formatter. However, I don't see project specific 
settings enabled for "Save Actions". Maybe that's the problem? Modifying that 
adds a bunch of "sp_cleanup..." stuff to .settings/org.eclipse.jdt.ui.prefs for 
me.

Oh, and please do continue to commit these changes to .settings. There's no 
downside to making everyone's Eclipse do the right thing automatically. 
However, as Richard points out, there may be some benefit to documenting our 
guidelines so that if anyone ever wants to work from another IDE (e.g. Netbeans 
or IntelliJ), they can continue to produce properly formatted code.

Original comment by steven.b...@gmail.com on 23 Jan 2011 at 1:49

GoogleCodeExporter commented 9 years ago
ok - I'm glad everything is working as planned with the uimaFIT project.  I'm 
not sure what the problem was with the ClearTK project.  I think I determined 
that the formatting profile gets saved in my workspace metadata - so I am not 
sure how you are seeing it.  

I am happy to close this issue as soon as we've documented a bit about our 
formatting guidelines.  

Original comment by phi...@ogren.info on 24 Jan 2011 at 3:08

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 18 Mar 2011 at 4:10

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 7 Jan 2013 at 4:51