Re: [JGIT PATCH 7/9] removing eclipse project files

[Robin Rosenberg <robin.rosenberg.lists@dewire.com>]

torsdag 24 september 2009 08:55:16 skrev Mark Struberg <struberg@yahoo.de>:
> Hi Ferry!
> 
> I work on a lot of projects and having eclipse (or any other IDEs) project files in the SCM is almost ever causing a problem. In praxis those files are always dirty. There are so many settings which may be different from user to user
> 
> * different versions of eclipse create different project settings
> * different JVM settings
> * changing profiler settings
> * using different version of various plugins
> etc, etc
> 
> And with maven in place we don't need to have them in our SCM anymore. Plus: it works for a lot of IDEs
> 
> You can easily create the project files for a few IDEs with maven e.g.:
> $> mvn eclipse:eclipse   for creating the eclipse project files
> $> mvn idea:idea         for creating the idea project files
> 
> Additionally, plugins are available for Eclipse [1], Intellij Idea (native, builtin) and NetBeans (native, builtin).
> 
> So most of the time it is enough to simply import the parent pom.xml and you get all things setup properly in your IDE.

I want compiler warnings/error and formatting settings to be enforced. Until recently we had roughly zero problems with non-confirming submissions

Is there some means for this, even if that would mean having access to only
a subset of possible settings. Maybe using checkstyle would do it for the
style checks. Not sure how we'd control formatting.

-- robin