re: Findbugs 1.1.1 Eclipse Settings

Message en plusieurs parties au format MIME
Brian,

I agree with Eugene and all others:
global settings must go in .metadata and
project settings must go in the project.
I think that storing .fbprefs in the
project root or in the .settings directory
of the project is not really
important (to have this file in the
project is important).

I am probably not alone in this case:
from time to time, I have to take some
of my projects on my desk PC to use
them on other computers (ee.g. laptops for
travels). When you import the projects
on the other PCs, it is very
interesting to retrieve the plugins
settings with the project. This currently
works for Findbugs and the other tools
I use (PMD, Lint4J....) and I expect to
be able to continue in this way.

I also agree with Andrei: those who
want to share their project settings can
check-in .fbprefs in their version control
tool; those who don't want to share
their settings don't check-in the file.
And I know teams sharing .fbprefs and
other teams not sharing it... Also,
for those who share their settings, don't
forget that changing the location of
the .fbprefs file from the project root
to .settings will oblige them to manually
take that change into account.

To give another point of view, in my
projects roots, I have preferences files
for PMD and Lint4J. PMD stores his global
settings in .metadata (Lint4J has no
global settings).

Philippe

On Tue Oct 3 14:05:30 EDT 2006, Brian
Cole wrote:
> On Oct 3, 2006, at 5:24 AM, Michael
Gerz wrote:
> > Hello everybody!
> >
> > Changes.html for findbugs1.1.1
states the following:
> >
> >   Eclipse plugin: project
data files now stored in .metadata (not  
> > in the project itself)
> >
> > I don't think that this is
a good idea. As a project manager, I  
> > would like to make sure that
all project members use the same FB  
> > settings. Therefore, I consider
".fbprefs" as part of my project  
> > (just like code style / formatting
/ etc.), not as a local setting.
> 
> Well, I did consider your point
of view, and I'm willing to change it  
> if enough people agree with you.
> The question is, what percentage
of you want to make sure that all  
> project members use the same
> settings? (With the proviso that
we're in the domain of shared  
> eclipse directories. If each project
> member has his/her own sandbox,
which is more often the case I think,  
> then this doesn't matter.
> Or does it??)
> 
> If one developer decides to check
the "Run findbugs automatically"  
> box, should that apply to all
> the other group members? Might
one developer want to disable all the  
> SQL-related detectors
> while another would want to see
those but disable all the  
> Serialization-related detectors?
> 
> I decided that moving .fbprefs
into the .metadata [getStateLocation 
> ()] instead of .settings
> [getWorkingLocation()] would be
better for the user population as a  
> whole. If project members
> want to be able to use different
settings they can. And it is at  
> least possible (though admittedly
> not convenient) for all project
members to have the same settings.  
> I'd like to hear all opinions on
this.
> 
> -brian
> 
> PS. Do we at least all agree that
the .fbwarnings file does indeed  
> belong in .metadata?
> 
> >
> > However, if you want to adhere
to Eclipse conventions, you should  
> > store that file in ./.settings,
not in the project's root  
> > directory. It would also be
beneficial if the file is somehow  
> > sorted internally. Each time
I make a single change the settings,  
> > the file looks completely
different (it even varies in size!) which  
> > makes it very difficult to
spot the differences.
> >
> > Kind regards,
> >
> > Michael Gerz