[ jEdit-devel ] jedit and findbugs

[Alan E. <ala...@gm...>]

I think there is no point in saving the XML file generated by findbugs
in Subversion - I agree with Vampire, it's a generated file that also
contains local path-specific filename references, which don't work on
other people's computers.

I just tried the eclipse findbugs plugin and it is very nice, by the way.
It loaded the .xml file I created from the regular findbugs GUI, and
shows me the errors in its own "bug tree view", with a detail dockable
that shows me more info in another dockable. Since I do most of my
java development in eclipse, I don't actually need a findbugs plugin
for jedit... But if such a thing were to exist, it would have to offer
similar features to the eclipse findbugs plugin. The regular error
list may need to be enhanced to handle the group by error category
feature, and also the findbugs plugin would need to have a detail view
of the bug.


On Dec 21, 2007 10:12 PM, Shlomy Reinstein <sre...@gm...> wrote:
> That's another idea, though it should be some "Generic" tracker issue.
> The issues reported by FindBugs are not easy to turn into real issues,
> some of them may even not be real issues.
> My current issue with jEdit failing to start happens only with the SVN
> trunk version and the release ProjectViewer version. I'm not even sure
> it has anything to do with what FindBugs reports.

the trunk version of projectviewer is by no means stable yet... And
had a lot of bugs, so I had to go back to 2.1.3.7 for my work.