Workspace settings vs project specific settings

I am thinking about the best way to keep the eclipse configuration for several developers consistent. By configuration I mean uniform

• compiler settings
• checkstyle configuration
• code formatter
• save actions
• file encoding

Thats are all things which the developers have to configure themselves in the eclipse preferences by working off a checklist. What do you think of configure everything project-specific for each project so the conf开发者_JS百科iguration can be checked in into version control? Then the developer just has to checkout/update the sources and all configuration is done already. Are there any disadvantages?

You can configure these at the project level and keep them in the code repository, but I've had problems with developers checking in their customized configurations before.

You might want to consider Robert Konigsberg's Eclipse Workspace Mechanic for managing Eclipse configurations.

There will be problem when some of the path are hard coded i.e. absolute instead of relative path.