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. Or is there anything missing? LieGrue, strub [1] http://m2eclipse.sonatype.org --- On Thu, 9/24/09, Ferry Huberts <ferry.huberts@xxxxxxxxxx> wrote: > From: Ferry Huberts <ferry.huberts@xxxxxxxxxx> > Subject: Re: [JGIT PATCH 7/9] removing eclipse project files > To: "Mark Struberg" <struberg@xxxxxxxx> > Cc: git@xxxxxxxxxxxxxxx, spearce@xxxxxxxxxxx > Date: Thursday, September 24, 2009, 8:29 AM > Mark Struberg wrote: > > All information necessary to build jgit is already > available in > > the maven pom.xmls. > > > > just out of curiosity, why would you remove the eclipse > files? > I for one - and I think many others - use Eclipse to work > on the code... > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html