Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Remove check for jacoco.append=true to disable caching"

This reverts commit 0ad7be70ca4661b5fdc56722a9018097b6797389.

+review REVIEW-6522

  1. … 3 more files in changeset.
Revert "Use a configure task to add jvmArgs to Test"

This reverts commit 8bb0429bc2140552c53dfbeb522c34a55caf63f0.

+review REVIEW-6524

  1. … 1 more file in changeset.
Use a configure task to add jvmArgs to Test

+review REVIEW-6524

    • -0
    • +52
    ./org/gradle/internal/jacoco/JacocoConfigure.java
  1. … 1 more file in changeset.
Remove check for jacoco.append=true to disable caching

If two Test tasks use the same JaCoCo execution data file, overlapping

output detection will disable build caching.

+review REVIEW-6522

  1. … 3 more files in changeset.
Remove deprecated methods in jacoco module

  1. … 1 more file in changeset.
First-class support for mapping between extension and task properties (#1452)

First-class support for mapping between extension and task properties

  1. … 36 more files in changeset.
Add missing @since and @incubation annotations

  1. … 10 more files in changeset.
Added `@Incubating` and `@since` to various types and methods.

  1. … 15 more files in changeset.
Report reasons for not caching (#1187)

We report the reasons why caching is disabled for a task. To that end you can call `cacheIf` and `doNotCacheIf` providing a description for the `Spec`.

It looks like it makes sense to call `cacheIf(Spec)` without providing a description when unconditionally enabling caching (e.g. `cacheIf { true }`).

For `doNotCacheIf` it always makes sense to provide a description why caching would be disabled. This is why we deprecate calling `doNotCacheIf` without providing any description while we do not deprecate calling `cacheIf` without providing a description.

Moreover, we moved resolving of task output caching state to an own executer. By this we know even for an up to date task if it is cacheable or not.

We evaluate cacheability of a task only if caching is enabled. If caching is disabled we use `DISABLED` as `TaskOutputCaching` in TaskStateInternal and do not log any message for each task.

+review REVIEW-6426

  1. … 24 more files in changeset.
Revert "Always re-run Test task when Jacoco is appending to its output file"

This reverts commit 886f8168ca2964aead95e7e2c8c1252c149fd282.

+review REVIEW-6420

Always re-run Test task when Jacoco is appending to its output file

+review REVIEW-6420

Do not cache Test task when Jacoco is appending to its output file

+review REVIEW-6420

Polish Javadoc

+review REVIEW-6418

Rename Jacoco’s classDumpFile to classDumpDir

Deprecated the old property in favor of the new.

+review REVIEW-6418

  1. … 5 more files in changeset.
Handle Jacoco’s `classDumpFile` as a directory

+review REVIEW-6418

Class-level annotation is good enough

Capture violations in Ant property

Throws any failure as GradleException instead of letting Ant take charge of it.

    • -0
    • +39
    ./org/gradle/internal/jacoco/JacocoCheckResult.java
Add Javadocs for setter methods

Inline spec to avoid exposure as public API

Fix inverse logic

  1. … 2 more files in changeset.
Fix method name and description

Do not introduce new methods that take Closure parameters

We can fully rely on Groovy SAM here.

  1. … 2 more files in changeset.
Align type with the one used in Maven plugin

  1. … 1 more file in changeset.
Use @Input to ensure incremental build is working properly

Use method that is not deprecated

Use Apache StringUtils instead of impl. from Plexus

Use latest JaCoCo version for multi-version tests

  1. … 3 more files in changeset.
Upgrade JaCoCo library to a Java 9-compatible version

  1. … 5 more files in changeset.
Change targeted release version

Use task name that better expresses intent

  1. … 13 more files in changeset.