-
Notifications
You must be signed in to change notification settings - Fork 50
Announcements
Version 2.5.0 now supports Gradle 4.0. In particular, the plugin has been enhanced to be aware of where Gradle 4.0 is putting class files. Prior versions of the plugin will run in Gradle 4.0, but it might not run correctly. See the CHANGELOG for more details.
Version 2.4.0 now builds under Gradle 3.2. It also introduces a change to the way the auxiliaryClasspath is set up. Previously, if you wanted to add to the auxiliaryClasspath, you would need to explicitly set all the elements.
Starting with version 2.4.0, you only need to specify the things you want to add to the default auxiliaryClasspath. Thanks to @Frank667 for the contribution.
Version 2.3.2 Groups tasks better, and allows applying the plugin from settings.gradle and init.gradle
Version 2.3.1 fixes a minor issue with Android projects, with thanks to Adam Peck (@dampcake).
The Gradle Cobertura plugin now supports Android projects, with thanks to Gautam Korlam (@kageiit). It is worth noting that unlike Java projects, where plugins can be applied in any order, using this plugin on Android projects requires that the Android plugin be applied before the Cobertura plugin.
At long last, Cobertura has released version 2.1, with thanks to Dennis Lundberg. As a result, the Gradle Cobertura plugin now uses version 2.1.1 of Cobertura by default. This version should play better with Java 8 and fix several of the issues users were having. As part of this release, I’ve bumped the version of Groovy that the plugin uses. This can cause issues in Gradle 1.×. The workaround is to add classpath ‘org.codehaus.groovy:groovy-backports-compat23:2.3.5’ to the buildscript dependencies.
- This version requires Gradle 1.0-milestone7
- Updated gradle api calls to no longer use deprecated methods.
- Changed name of published artifact to include version number.
- Added coberturainit.gradle script to make application of plugin easier and less messy.
- Removed add of ‘mavenCentral()’ to project repositories. Some maven repository is required to get the plugin to work and mavenCentral was conflicting with a local Artifactory install.
- Initial upload of plugin
- See Cobertura Plugin Wiki for documentation