according to maven you should not check in .project and .classpath. the .settings can savely be committed because like gwyn says they are for code style etc and maven does not touch them.
Maurice On 9/6/07, Gwyn Evans <[EMAIL PROTECTED]> wrote: > On Thursday, September 6, 2007, 10:33:55 AM, Ate <[EMAIL PROTECTED]> wrote: > > > Any reason why eclipse project configuration files (.classpath, > > .project, .settings/) are checked in? > > Each time I run mvn eclipse:eclipse (from the root) the .classpath > > file is modified as the plugin rewrites the order of the > > dependencies. > > As no other project has these files checked in, I'd like to remove them. > > Any objections? > > I don't use Eclipse myself, but aren't the .settings/ files defining > the standard code-style to use for the project? It might be that they > should be retained... > > /Gwyn > >
