Gradle Errorprone Plugin V0.0.x Versions Save

Configure tasks lazily in Gradle 4.9 (#73)

• Display a warning if the default (latest.release) dependency is used (#71). Using latest.release (and generally speaking, changing or dynamic versions) is discouraged, see the rationale in the README (2900871)
• Track the errorprone configuration to determine whether compilation tasks are up-to-date (#72). The check is more accurate in Gradle 4.3 and more recent versions.

Better support for JDK 9 (#64)

You might want to try out the net.ltgt.errorprone-javacplugin plugin for Java 9+ though, particularly as net.ltgt.errorprone does not support Java 10+.

The plugin now uses the latest.release version of Error Prone by default.

The plugin is now compatible with Gradle 1.12 (#2, d2a7a5250c9f7bcf607a6f79d123acae5da001c6).

The plugin is now compatible with Gradle 2.1 (#4, 93799671ebbde85f0aadbf201eb5f36da3cffa4b). Not that it is however no longer compatible with earlier versions.

The plugin is now compatible with Gradle 2.2. Not that it is however no longer compatible with earlier versions.

• The plugin is now compatible with Error Prone 2.x, which makes it compatible with JDK 8 (#5, #6)
• The plugin is now available on the Plugin Portal, through the new plugin IDs net.ltgt.errorprone-base and net.ltgt.errorprone. The previous IDs (errorprone-base and errorprone) are still available when using the apply plugin: syntax.

• The plugin is compatible with Gradle 2.4 (#8). Note that it is however no longer compatible with earlier versions.
• The plugin is now published to the Plugin Portal. It is no longer published to The Central Repository (aka mavenCentral())

Fixed the description in the Plugin Portal (#9, 9e7d116d2c4137b2b4b45e94afc63e90f8e7ecb0). No other change from v0.0.7