Release 3.4
* Additional build status thresholds: now you can set the build status to unstable or failure if the total number of the number of new warnings exceeds the defined thresholds ([2537@issue], [3024@issue]).
* Improved new warning detection: now warnings are only considered as new if the associated source code context (3 lines of code) differs.

Release 3.3
* Fixed auto-configuration of native m2 jobs when the maven site goal is used ([2892@issue], [2880@issue])

Release 2.20
* Added zero warnings high score status: you will see if you reached a new high score (e.g., the time your build stays in a zero warnings state). If you have a zero warnings build, but no high score yet then you will see the number of days still to go until you reach the high score.
* Copy files that contain annotations from slave to master ([1749@issue], [2371@issue])
* Fixed overall module summary in m2 jobs (wrong number of scanned files: [2347@issue])

Release 2.19
* Improved performance of relative file name resolution (thanks to Alfred Messner for the patch)
* Fixed wrong links to package and module details if the name contains illegal hyperlink characters ([2476@issue]).
* Tables are now sorted by the first column on loading ([2464@issue]).
* Show short warning message of the FindBugs team if the build has not been configured to produce the XML format with messages ([2458@issue]).

Release 2.18
* Fixed {{FileNotFoundExceptions}} if plug-in is used in a master slave setup ([2371@issue]).

Release 2.15:
* Use maven properties to initialize the source folders of the findbugs-plugin source finder ([2052@issue], [2287@issue])
* Fixed width and tooltips of the summary images that show the distribution per module, package, etc.
* Fixed tab view rendering for internet explorer
* Fixed display of filenames if there is no path segment in a filename ([1727@issue])

Release 2.14:
* Enhanced health and stability evaluation: added configuration of severities that should be considered during evaluation ([2003@issue], [2202@issue])
* New and fixed warnings of are now computed using the refactoring-aware hash codes of the findbugs plugin ([731@issue])
* Fixed parsing of findbugs files if Hudson is deployed in JBoss container ([1991@issue])

Release 2.13:
* Show spinner image during loading of tab content.
* Added number of items in the label of a tab.

Release 2.10:
* Added different help texts for maven or freestyle configuration
* Parsing of ant build.xml or maven pom.xml files is now only done if the build runs with the corresponding runner ([1898@issue])
* Ignore maven projects without target folder ([1813@issue])
* Reduced mermory footprint of parser ([1960@issue])
* Fixed NPE during computation of new warnings ([2093@issue])
* "Zero warnings since build #x" indicator should work correctly now ([1533@issue])
* Height of trend graph can be changed for the m2 project type, too ([2115@issue])

Release 2.9:
* New file overview page that shows the distribution per file
* Added source code links to warnings table
* Show line number of files in all warning detail views ([1974@issue])
* Improved layout (css) of the tabview

Release 2.8:
* New result UI with drill-down and statistics of modules, packages, severities, categories, types, overview, details, fixed and new warnings
* Added parsing of ANT build.xml files to extract the project name ([1560@issue])
* Improved parsing of Java files to extract the package name ([1828@issue], [1829@issue])

Release 2.7:
* Fixed update of configuration if the FindBugs plug-in is used in conjunction with violations plug-in ([report|http://www.nabble.com/checkstyle-and-pmd-plugins-don%27t-save-result-pattern-settings-tp17460463p17460463.html])
* Fixed exception during parsing of FindBugs warnings of priority experimental ([1801@issue])

* Highlighting of single lines as well as line ranges
* Highlighting of multiple line ranges per warning (different color for primary range)
* Extraction of module/project names from FindBugs files
* Added support for native m2 build option of Hudson
* Errors during parsing are reported on an error screen (no build failures anymore)
* Improved detection of source code files (for source highlighting)
* Shows since which build we have zero warnings

Release 1.18
* &nbsp;Fixed issue where there was only one warning reported per class for ant generated findbug reports ([issue #930|930@issue])

Release 1.16
* Added highlighting of the source code line that contains the warning
* Added toggle link for the trend graph: if failure or healthy thresholds are defined, then you could use this link to toggle between two graph modes.

** Priorities mode: the graph shows the distribution of warnings by priority

Release 1.10
* Mapping of warning to source files is now persisted (should be faster for large workspaces)
* Fixed mapping of warnings to classes if there are more than one warnings in a file.
* Fixed serialization problem when compiling on a remote machine ([868@issue])

Release 1.9
* Added direct links to source code to jump to the warning (for the current build only).

Release 1.1&nbsp;
* Warning files are parsed now and shown in a package overview and details view
* The difference of new and old warnings is calculated and shown for each package
* Added a detail pane that shows the individual warnings in a selected package
* Configuration parameters will be validated now
* Added new icons (The FindBugs logo is a trademark by The University of Maryland. These icons are a courtesy of the FindBugs team.)
* The trend graph is only shown if there are at least two result points
* Bugfix: failed/succeeded build mails are correctly sent now