Displaying 1 to 17 from 17 results

SpotBugs - FindBugs' successor, A tool for static analysis to look for bugs in Java code.

  •    Java

SpotBugs is the spiritual successor of FindBugs, carrying on from the point where it left off with support of its community. SpotBugs is a program which uses static analysis to look for bugs in Java code.

gradle-static-analysis-plugin - Easy setup of static analysis tools for Android and Java projects.

  •    Groovy

A Gradle plugin to easily apply the same setup of static analysis tools across different Android or Java projects. Gradle supports many popular static analysis (Checkstyle, PMD, FindBugs, etc) via a set of built-in plugins. Using these plugins in an Android module will require an additional setup to compensate for the differences between the model adopted by the Android plugin compared to the the Java one.

fb-contrib - a FindBugs/SpotBugs plugin for doing static code analysis for java code bases

  •    Java

An auxiliary findbugs.sourceforge.net plugin for java bug detectors that fall outside the narrow scope of detectors to be packaged with the product itself.

static-code-analysis-plugin - A plugin to simplify Static Code Analysis on Gradle

  •    Groovy

Static Code Analysis wraps around Checkstyle, Findbugs, PMD and CPD, offering new features and extensions to the encapsulated plugins, making it easier to use them and providing better results with minimum effort. The plugin is compatible with Gradle 2.3+, Gradle 3.0+ and Gradle 4.0+. We are commited to supporting at least the last 2 major gradle versions.

gnag - A Gradle plugin that helps facilitate GitHub PR checking and automatic commenting of violations

  •    Java

Gnag is a Gradle plugin that helps facilitate GitHub PR checking and automatic commenting of violations for Android projects. It can be used in Java-only, Kotlin-only, and mixed Java/Kotlin codebases.

JSR305CheckstylePlugin - a plugin which ensures nullness annotations on methods and constructors

  •    Java

A checkstyle plugin which ensures nullness annotations on methods and constructors. Copy JSR305Checkstyle-x.x.x.jar into your eclipse dropins directory or add it to the classpath of your checkstyle task.

findbugs-android - Gradle plugin that creates FindBugs reports for android projects

  •    Groovy

In order to create FindBugs report for Android projects, you need to create FindBugs tasks and configure them by providing paths to source code, compiled classes and classpath. It can be troublesome since Android projects can have different flavors and build types, thus requiring additional paths to be set. This plugin provides those tasks already configured for you. In addition, the plugin automatically excludes Generated classes from Android databinding library, android resource, Butterknife and Dagger 2. If you want more added to this list or want it configurable, open an issue.

sputnik - Static code review for your Gerrit patchsets

  •    Java

Sputnik runs Checkstyle, PMD, FindBugs, CodeNarc, JSHint (or JSLint), TSLint, Ktlint, Detekt and Sonar only on files affected by Gerrit's patchset. It collects all violations and report them back to Gerrit or Stash. If you want sputnik to use your SonarQube rules just download them from your SonarQube profile and use these with checkstyle.configurationFile, pmd.ruleSets and findbugs.includeFilter variables.

gradle-circle-style - A plugin for Gradle that summarizes build failures in CircleCI, especially Checkstyle and FindBugs

  •    Java

A plugin for Gradle that summarizes failed Gradle builds in CircleCI, with special handling for Checkstyle and FindBugs failures. This plugin is enabled by the CIRCLE_TEST_REPORTS environment variable, set automatically on CircleCI builds. It then automatically enables XML output for Checkstyle and FindBugs plugins, and adds a finalizer task that collates their results (and any other Gradle build step failures) using the JUnit XML output that CircleCI expects.

okcheck - Incremental scan,integrate Lint、KtLint、UnitTest、Checkstyle、Findbugs、Pmd, powerful and easy to use

  •    Groovy

Incremental scan,integrate Lint、KtLint、UnitTest、Checkstyle、Findbugs、Pmd, powerful and easy to use. Done! Everything is ready to scan, now you can check with 6 job just run ./gradlew okcheckDebug and just see result, and all report is settle down the build/reports for the root project as default(But if you want all reports save on the origin directory, just set destination to project.buildDir).

android-gradle-java-mutli-module-template - Static analysis tools: PMD, Findbugs, Checkstyle, Lint and Jacoco on multi module build with an Android app module, Android library module and a Java module

  •    Java

This demonstrates running source analysis tools(PMD, Findbugs, Checkstyle, Lint and Jacoco) on multi module build with an Android app module, Android library module and a Java module. This project builds with Gradle and the Android Build tools.

gradle-code-quality-tools-plugin - Gradle plugin that generates ErrorProne, Findbugs, Checkstyle, PMD, CPD, Lint, Detekt & Ktlint Tasks for every subproject

  •    Groovy

Gradle plugin that configures Error Prone, Findbugs, Checkstyle, PMD, CPD, Lint, Detekt & Ktlint. All of these tools are also automatically hooked into the check gradle task. Below, I'll go more into depth how each of those plugins are configured. The philosophy of this plugin is to fail early. This means having zero warnings / errors reported from any tools. If you're just getting started with this in a large code base you might not be able to achieve this right away in which case you might want to set failEarly to false and then apply at a finer more granular scope how each tool should behave e.g. checkstyle { ignoreFailures = false }.

sbt-findbugs - FindBugs static analysis plugin for sbt.

  •    Scala

This sbt plug-in enables you to analyze your (Java) code with the help of the great FindBugs tool. It defines a findbugs sbt action for that purpose. And then run the plugin with sbt findbugs. This will generate a FindBugs report in target/scala-xx/findugs/report.xml.

gradle-quality-plugin - Gradle quality plugin for Java and Groovy

  •    Groovy

Static code analysis for Java and Groovy projects using Checkstyle, PMD, SpotBugs (FindBugs) and CodeNarc. Plugin implements unified console output for all quality plugins which greatly simplifies developer workflow: only console is required for working with violations and makes it feel the same as java compiler errors. Releases are published to bintray jcenter, maven central and gradle plugins portal.

android-quality-starter - setup CheckStyle, FindBugs, PMD and Lint for your Android project easily

  •    Shell

This project adds gradle setup for quality tools mentioned above to Android project via shell script. After adding this, we can easily increase quality of the project by static code analysis. This project is inspired by vb-android-app-quality application.

cjp-examples - Examples from the Checking Java Programs book and videos

  •    Java

I’ve been an advocate of advanced techniques and strong testing for most of my life as a software developer. This repository was first set up in 2007 (in CVS; moved to GitHub in 2015). It was originally built with Ant but has mostly been moved to Maven to simplify classpath. Classpath is also the reason I chose to split this repo into multiple projects, each an Eclipse project and a Maven-buildable project. Otherwise the classpath (and the Maven pom file) would become overly large. Not everything builds or runs at the moment: patches welcome; complaints, not so much. A few parts of this will indeed likely stay on Ant because one or two of the tools are only available as Ant plugins. While I do know about the maven-ant-plugin, it’s still just easier this way.