From: SourceForge.net <no...@so...> - 2003-06-04 18:19:23
|
Feature Requests item #749045, was opened at 2003-06-04 13:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=438938&aid=749045&group_id=44253 Category: User interface Group: None Status: Open Priority: 5 Submitted By: Peter Centgraf (centgraf) Assigned to: Nobody/Anonymous (nobody) Summary: FindBugs Integration Initial Comment: I would like to see some integration of the excellent FindBugs tool from the University of Maryland with DrJava. The two stories below describe two potential levels of integration, for the short-term and long-term, respectively. Sort-Term Story: A user is editing several documents in DrJava and wishes to run FindBugs on the associated class files before submitting their work. They select "FindBugs" from the Tools menu. DrJava launches a new instance of the FindBugs GUI, passing it the locations of the classfiles associated with the current open documents and the user's current classpath. The user can then use FindBugs as usual, referring back to the documents in DrJava manually. Longer-Term Story: A user wishes to run the FindBugs filters on the currently opened documents. They select "FindBugs" from the Tools menu. DrJava uses the FindBugs patterns with the current documents and classpath, displaying a new tab with a progress bar a la the JUnit tab. When the analysis is complete, the pattern hits are displayed in the tab with the same style of interaction as errors from the compiler, JUnit, or Javadoc, including the ability to jump to hit locations and edit the source in question. The FindBugs support could also be integrated with any notion of projects which we might add to DrJava. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=438938&aid=749045&group_id=44253 |