From: Matthieu C. <cho...@gm...> - 2007-12-21 07:57:06
|
More than launching findbugs and parse the result, I think it is possible to integrate findbugs in a plugin through an api. There are plugins for other IDEs like eclipse, why not jEdit Matthieu On Dec 21, 2007 1:09 AM, Alan Ezust <ala...@gm...> wrote: > I agree. I have still yet to see findbugs fully in action, but it's on > my list of things to do now. > I think a plugin that runs and parses findbugs output and shows it in > the error list would be preferable to storing the findbugs output in > the svn. > > > On Dec 20, 2007 3:18 PM, Dale Anson <da...@gr...> wrote: > > Great idea! A FindBugs plugin would be a nice addition to jEdit too. > > > > Dale > > > > > > > > Shlomy Reinstein wrote: > > > I just ran the FindBugs utility (http://findbugs.sourceforge.net/) on > > > jEdit and it has found quite a few threading/synchronization problems, > > > some of them in the thread/thread-pool classes. I will check them, but > > > for those who are interested, FindBugs usually reports real problems. > > > It helped me detect threading problems quickly when I developed the > > > GdbPlugin. > > > How about adding the FindBugs output for jEdit to SVN? It's an XML > > > file as far as I remember, which can be loaded by anyone. As problems > > > are fixed, we can redo the processing and save the updated FindBugs > > > output. > > > > > > Shlomy > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-devel > |