From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date: Mon, 28 Sep 2009 06:34:44 GMT
Subject: Re: [JGIT PATCH 7/9] removing eclipse project files
Message-ID: <200909280834.45360.robin.rosenberg.lists@dewire.com>
In-Reply-To: <2c6b72b30909271921y4b191f1fo42b1ffb5f08d3468@mail.gmail.com>

måndag 28 september 2009 04:21:36 skrev Jonas Fonseca <jonas.fonseca@gmail.com>:
> On Sun, Sep 27, 2009 at 15:52, Robin Rosenberg
> <robin.rosenberg.lists@dewire.com> wrote:
> > lördag 26 september 2009 22:10:16 skrev Mark Struberg <struberg@yahoo.de>:
> >> And there is a lot more which imho cannot be set for a project. So checking in the xml sounds like it is way more powerful isn't? And we would have this
> >
> > For JGit, not really. Everything that is not project settings should be left as the default. The only reason is tool constraints. I'm not well versed
> > enough to tell what neatbeans does here.
> 
> It is my impression that NetBeans has far better integration with
> maven. In terms of code formatting NetBeans supports
> exporting/importing project specific settings, but I have never
> personally used that.

I was thinking of (project) settings for controlling warnings/errors and formatting.

-- robin