Brian,
Can't you just use different strategies for saving settings Eclipse
and standalone version? So, you could use Eclipse API to store these
settings.
That would resolve potential side effects of these settings getting
out of sync, particularly critical for VCS plugins... Otherwise you
would have to work around that by explicitly refreshing that file after
each update.
regards,
Eugene
Brian Cole wrote:
As you may have already noticed, the location of the .fbprefs file has
reverted back to the root directory of each project. So 1.1.1-rc1 was
the only release in which .fbprefs was outside of the project directory.
Several of you have mentioned that it should actually be stored in the
project's .settings directory. I like that idea, but I'm having
trouble finding any Eclipse documentation to corroborate this. The
code in org.eclipse.core.internal.resources.ProjectPreferences
creates/reads/writes files in the .settings directory, but the
FindBugs plugin doesn't use the Eclipse preference APIs. Do Eclipse
conventions permit the FindBugs plugin to place a custom file in the
.settings directory? (I see no API to retrieve the directory or its
name, but I could certainly hard-code ".settings" into the path and
choose a file name that is unlikely to conflict with anything.) If
anyone has links to Eclipse documentation in this area, I'd love to
see them. I've had trouble finding decent Eclipse documentation.
In any case, from now through the final 1.1.1 release the location of
.fbprefs will be as described in the first paragraph. I apologize for
any trouble you had with 1.1.1-rc1.
(As for the .fbwarnings file, it moved into workspace .metadata
starting with 1.1.1-rc1 and will remain there.)
-brian
_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@xxxxxxxxxxxxxxxxxx
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
| 