Question

When invoking importing maven projects into eclipse from git using “Import Maven Projects” the m2e plugins to seems to generate a new .project and .classpath and some other files even though those files are checked in.

To get around this problem I would like to not check in any eclipse specific files, but there are customizations made to each project file such as custom save actions, or changes to the validation to ignore specific things, or changes to the javascript configuration for a dynamic web project that need to be preserved, so either those files need to checked or those settings need to be generated by m2e.

Any way to use m2e to configure the eclipse project validators?

Answer 1

We had a similar problem in the past. We solved it by

• don’t checkin eclipse specific files (svn ignore, git ignore, …)
• Use Workspace Mechanic plugin to keep eclipse settings the same accross development machines / developers.