|
Re: export question [message #707552 is a reply to message #707468] |
Mon, 01 August 2011 19:56 |
|
Hi
We do version control the .settings directory for the following reasons:
- We keep as much configuration as possible on the project level. A
workspace-level configuration of things like compiler settings,
formatter or auto save actions is not possible in our case as most of
our engineers work on different projects having different needs.
- We use Maven and some projects prefer m2eclipse and some the maven-
eclipse-plugin. Whether the .classpath files are checked in is
therefore a permanent discussion...
- In a large project we use the maven-eclipse-plugin not only to
configure the .classpath but also to add/ensure some config files
like jdt prefs. In that case we have a Hudson job doing the
eclipse:eclipse and a check-in regularly so that our team just
consumes the results.
Back to your questions: I think there is no final answer. It depends on
how your team wants to work and which other (build) tools you use.
Take care,
Michael
|
|
|
|
Powered by
FUDForum. Page generated in 0.05051 seconds