Search Results for "findbugs"

SpotBugs is a program that uses static analysis to look for bugs in Java code. It is free software, distributed under the terms of the GNU Lesser General Public License. SpotBugs is a fork of FindBugs (which is now an abandoned project), carrying on from the point where it left off with the support of its community. Please check the official manual for details. SpotBugs requires JRE (or JDK) 1.8.0 or later to run. However, it can analyze programs compiled for any version of Java, from 1.0 to 1.9. To build the SpotBugs plugin for Eclipse, you'll need to create the file eclipsePlugin/local.properties, containing a property eclipseRoot.dir that points to an Eclipse installation's root directory (see .travis.yml for an example), then run the build.

Automatic correction of software bugs announced in compilers (clang, gcc) / Static Code Analysis tools (cppcheck, FindBugs) and grammar/style errors like in LanguageTool. Usage: use tool (e.g. cppcheck) and store results in a text file. Afterwards call: autoreplacerplus mytextfile

FindBugs plugin development: Java class header checker

A static analysis tool to find bugs in Java programs.

...中文版(ChineseVersion) https://sourceforge.net/projects/visualstudioscan/files/Document/VS_Code_Scan_Assistant_Help_Chinese.docx/download English Version https://sourceforge.net/projects/visualstudioscan/files/Document/VS_Code_Scan_Assistant_Help_English.docx/download VisualStudio_Scan is a Visual Studio plugin for static analysis of C/C++ code. It not only covers the features provided by other analysis tools such as cppcheck, coverity,pclint, findbugs and PMD, but also provides many benefits that others are not offering. It debugs the types of bugs that are hardly detected by the compilers and also highly reduces fixing costs. Not depending on compilers enables it to find potential quality issues efficiently (100,000 line per minute). It can find critical issues such as null pointer dereference, memory leaks, buffer overrun, and logic errors

...The checks provided here are typically used to validate method parameters and detect errors during runtime. To detect errors before runtime we use JSR-305 Annotations. With these annotations you are able to detect possible bugs earlier. For more informations look at FindBugs™ JSR-305 support. We noticed that many projects just copy org.springframework.util.Assert or com.google.common.base.Preconditions to get access to these quality checks. Therefore we provide these features and small library that can be included in any application without big overhead.

Yasca is an open source program which looks for security vulnerabilities, code-quality, performance, and conformance to best practices in program source code, integrating with other open-source tools as needed. Yasca has been migrated to Github, and is available at http://scovetta.github.com/yasca and http://github.com/scovetta/yasca.

Cathcart is a collection of Apache Ant tasks and a Maven plugin for checking trends in software metrics (generated by junit, jmeter, clover, pmd, findbugs, cobertura etc). Use Cathcart to ensure continuous improvement in software quality.

This is an Oracle Jdeveloper 11g plugin for using findbugs.

Code Quality Plugin (CQP) is an Eclipse plug-in, built on top of existing tools such as Checkstyle, Findbugs, JDepend to help realize code quality standards. CQP gives a snapshot of the quality of code during development.

The Maven Author Plugin generates an HTML report showing informations gathered from other Maven reports (Checkstyle, FindBugs, PMD, Lint4j, JavaNCSS, JCoverage, Cobertura, Emma, Clover, Tasks List, etc.) and categorized by author(s) of source files.

QALab collects and consolidates data from several QA tools, like pmd, checkstyle, FindBugs, Cobertura and Simian and keeps track of them overtime. This allows developers,architects and project managers alike to be presented with a trend of the project QA

MetaCheck is a java code checking utility to convert results from various code checking tools (jcsc, pmd, checkstyle, findbugs, ...) into one uniform xml/html result for each of the checkers and for the generated meta result.