4.1.1 (Mar 20, 2017)

This release fixes a problem where the new option introduced in the previous release was not properly reflected in the configuration data for the Eclipse and SonarQube plugins.

[Which files to choose for download?]

4.1.0 (Mar 17, 2017)

This release introduces a new flag called failQuietly to the ModuleDirectoryLayout check. When this new flag is set, set check disables itself when it does not find its directory configuration. This helps when the check is centrally configured, but not all checked projects supply a configuration.

[Which files to choose for download?]

4.0.1 (Mar 13, 2017)

A minor bugfix to the ModuleDirectoryLayout check which enables correct handling of files located directly in a project’s baseDir, in the case where that project has a defined structure of submodules.

[Which files to choose for download?]

4.0.0 (Feb 20, 2017)

This release contains only minor enhancements, such as a new placeholder that is available for the propertyFile option of the PropertyCatalog check.

This is a new major version because starting with Checkstyle 7.0, Checkstyle requires Java 8. So Checkstyle Addons is now also compiled for Java 8 by default. If you are on a previous Java version, that’s fine! You may use the artifacts postfixed with java7 or java6, respectively. They are functionally equivalent, but work with previous levels of Java and the corresponding older versions of Checkstyle.

[Which files to choose for download?]

3.0.0 (Apr 30, 2016)

We have a new check called ModuleDirectoryLayout which helps ensure that the modules within a project follow a configurable directory layout such as the Maven Standard Directory Layout. Also, there are some minor improvements to the RegexpOnString check and minor fixes.

This is a new major version because the dependency structure has changed. We now depend on some external libraries other than Checkstyle. IntelliJ and command line users will have to use the new -all artifact which includes the external libraries so that nothing else needs to be downloaded.

[Which files to choose for download?]

2.1.1 (Mar 09, 2016)

This is a small release that just adds better String detection to the RegexpOnString check.

[Which files to choose for download?]

2.1.0 (Feb 27, 2016)

This release adds two new features to Checkstyle Addons: - A new check: RegexpOnString, which helps finding String literals which match a regular expression (for example, find hard-coded host names) - The placeholders in the propertyFile option of the PropertyCatalog check were extended to include {11}, which evaluates to dynamic module roots, thus allowing a fixed check configuration to be applied to different projects with different module structures.

[Which files to choose for download?]

2.0.0 (Feb 08, 2016)
No release notes available for this version yet.
1.3.2 (Aug 24, 2015)

This is a bugfix release which addresses a minor bug in the PropertyCatalog check, which occurred when people used separator characters in their checkstyle configuration which did not correspond to the system-defined separator (for example, forward slashes on Windows).

1.3.1 (Jul 31, 2015)

This is a technical release which introduces a separate publication for Java 6 legacy environments. It also improves handling of binary names in the presence of unusual characters (such as inner classes called $).

The build process was improved substantially, so it can now check the compatibility of Checkstyle Addons code with every reasonably recent Checkstyle version. An internal component was introduced which smoothes over the breaking API changes between Checkstyle versions. In this way, it is now possible to offer two distinct variants of Checkstyle Addons: - checkstyle-addons-java6, which requires the analysis process to run on Java 6 or later, and is compatible with Checkstyle 6.0 - 6.1.1 - regular checkstyle-addons, which requires the analysis process to run on Java 7 or later, and is compatible with Checkstyle 6.2 - 6.8.1 (and, hopefully, more recent versions as they become available)

Note that on every build, the build process actually tries running against the different Checkstyle runtimes, so the compatibility statement is based on the fact that it worked. Building for one particular Checkstyle version is no longer required (although possible, by calling gradlew main681Classes, where 681 is the Checkstyle version).

1.3.0 (Jul 09, 2015)
  • New check: LocationReference - This check can be configured to compare a method argument or variable assignment to the names of the current method or class, helping to make sure that such code location references are correct.
  • Reacting to the high volatility of the public Checkstyle API, Checkstyle Addons is now automatically built against all Checkstyle versions requiring at least Java 6 (which is 6.0 and upwards). This means more work for the build server, but also much higher confidence that the Checkstyle Addons code will be compatible with any Checkstyle version.
  • The previous item is supported by the introduction of dependency configurations. A dependency configuration is a property file which lists the versions of things that we depend on when building for a particular Checkstyle version, for example Java level, or SonarQube plugin versions.
  • Minor improvements to the inner code quality
1.2.1 (Jun 13, 2015)
  • PropertyCatalog: New property ‘baseDir’ to better enable certain IDEs
  • PropertyCatalog: New placeholders for property file path construction
  • Add workaround for Checkstyle bug #1205
  • Several small improvements to the build process and documentation
1.2.0 (Jun 10, 2015)

New check: PropertyCatalog - helps keep a property file in sync with a piece of code referencing the property keys New property in IllegalMethodCallCheck: excludedQualifiers

1.1.0 (May 29, 2015)

New check: IllegalMethodCall

1.0.1 (May 14, 2015)

No change over 1.0.0. This is a technical release to connect to Maven Central.

1.0.0 (May 03, 2015)

This is our initial release. So far, there are only two checks, but they are ready to rock!