Skip to content

Releases: scoverage/gradle-scoverage

3.1.0

22 May 21:18
Compare
Choose a tag to compare
  • #100 Collect scoverage from all tasks - thanks @alisiikh
  • #99 Performance enhancement - thanks @tpetrov-rms

3.0.0

24 Feb 22:58
Compare
Choose a tag to compare

Thanks to @eyalroth for the recent updates.

  • Auto resolution of scalac plugin dependencies.
  • Aggregation task declared by default.
  • Deletion of non-instrumented classes, allowing for better integration with other coverage tools such as cobertura.
  • Ability to execute coverage without "normal" compilation, thus reducing build times.

2.5.0

20 Oct 20:51
Compare
Choose a tag to compare

Bug fixes:

  • #81 IOException on Windows when registering task output files

2.4.0

29 Sep 17:44
Compare
Choose a tag to compare

Bug fixes:

  • #78 compilation is duplicated
  • #74 testing of covered code is not cached

Additional features:

  • scoverage tasks are now part of the verification group

2.3.0

11 May 20:16
Compare
Choose a tag to compare
  • Cachable tasks
  • Removes the unexpected dependency on scalac-scoverage_2.11 from version 2.2.0 published to the Gradle plugins portal

2.2.0

08 May 21:14
Compare
Choose a tag to compare
  • better support for the Gradle build cache
  • support implementation and testImplementation configurations

2.1.0

21 Aug 19:39
Compare
Choose a tag to compare
  • Remove support for the Ant compiler as it is removed from Gradle 3.0

2.0.1

17 Jan 08:35
Compare
Choose a tag to compare

Fix #55 - code in src/main/java is not correctly compiled

2.0.0

29 Dec 14:16
Compare
Choose a tag to compare
  • Publish the plugin to the gradle plugin repository.

This requires a change to the plugin identity to meet their convention.

apply plugin: 'scoverage'

becomes:

apply plugin: 'org.scoverage'

or you can use the new plugin mechanism:

plugins {
  id 'org.scoverage' version '2.0.0'
}

1.2.0

29 Dec 14:13
Compare
Choose a tag to compare
  • include scoverage jars in the runtime dependencies of the instrumented classes. This simplifies the use case where there are multiple forms of test which should be included in code coverage measurements. It may represent a breaking change for some users.