FindBugs
 
Docs and Info
FindBugs 2.0
Demo and data
Users and supporters
FindBugs blog
Fact sheet
Manual
Manual(ja/日本語)
FAQ
Bug descriptions
Mailing lists
Documents and Publications
Links
 
Downloads
 
FindBugs Swag
 
Development
Open bugs
Reporting bugs
Contributing
Dev team
API [no frames]
Change log
SF project page
Browse source
Latest code changes

Contributing to FindBugs

If you have a bug fix or feature enhancement you would like to contribute, we would be happy to consider it for inclusion.

Import FindBugs code as Eclipse projects

The preferred way to get the FindBugs source code and create the patch is to use Eclipse + SVN. You can easily import FindBugs code into Eclipse by following the steps described here: Import Eclipse projects .

Preparing a patch

The best way to send an enhancement is to create a patch against the latest code in the FindBugs Subversion repository at http://findbugs.googlecode.com/svn/trunk/ (those people who have been given commit priviledges should use https://findbugs.googlecode.com/svn/trunk/).

To create a patch from Eclipse, please right click the [findbugs] or [findBugsEclipsePlugin] project and choose [Team | Create Patch...] context menu.

Please follow these guidelines when preparing your patch:

  • Use the same indentation style as the source file(s) you are modifying.  In particular, please use tabs (not spaces) to indent your code; one tab per indent level.
  • If at all possible, avoid making whitespace modifications.
  • Small patches are appreciated.
  • If you are submitting a new bug detector, please submit a small standalone source file that contains an instance of the kind of bug the detector looks for.

Following these guidelines makes it much easier for us to incorporate new code.

How to submit a patch

Patches may be submitted through the Patches tracker on the sourceforge project page.


Send comments to findbugs@cs.umd.edu

SourceForge.net Logo