Brian,
Why don't you follow common Eclipse model? Store global settings in
.metadata and if enabled, store project specific settings in
project/.settings folder like I suggested while ago.
WRT .fbwarnings I agree with you, it is better to store it in .metadata.
By the way, I wonder why it is not possible to run FindBugs only on
selected folder or clean fb markers from the selected folder? Currently
it is always runs on the whole project.
regards,
Eugene
Brian Cole wrote:
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
_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@xxxxxxxxxxxxxxxxxx
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
| 