Re: re: Findbugs 1.1.1 Eclipse Settings

On Tue, 03 Oct 2006 20:05:30 +0200, Brian Cole <tuc@xxxxxxxxxx> 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.

100% ack

> 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??)

All project settings belongs to the .settings folder of project. It's on  
customers to decide how they manage projects and their settings. In all  
our projects all project settings files are shared to insure that each  
project member could see all warnings/errors etc, and to have consistent  
state across different workstations.

> If one developer decides to check the "Run findbugs automatically" box,  
> should that apply to all
> the other group members?

As long as this developer does not check in the changes, nothing happens.  
But this decision to run or not run findbugs is usually made by project  
manager :)

> 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?

See above.

> 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.

It's an Eclipse pattern to save *plugin* preferences which are not project  
related into .metadata directory, and *project* preferences into the  
.settings directory in the project. In this way it is always possible use  
version control for such settings, which is MUST for compiler settings,  
checkstyle warnings and even findbugs settings.

> -brian
>
> PS. Do we at least all agree that the .fbwarnings file does indeed  
> belong in .metadata?

Yes, or, better, in the "bin" or better "usr/temp" directory. It's  
"derived" resource and shouldn't appear under the project root.


--
Kind regards,
mit freundlichen Grüßen
Andrei Loskutov

@Home: http://andrei.gmxhome.de
Hinweis: diese Nachricht besteht nur aus den wiederverwertbaren Bits.