Gradle

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Do not append to Jacoco output in tests

So that the task is cached/can be up-to-date

+review REVIEW-6420

Temporarily disable WorkerDaemonServiceLoggingIntegrationTest

Test if beforeTaskOutputsGenerated() is called

+review REVIEW-6419

restrict cross version tests to gradle >2.5

- we use progress listener in the test which was not available before gradle 2.5

+review REVIEW-6414

Do not fail if non-cacheable task has non-optional null output file

+review REVIEW-6421

    • -1
    • +9
    /gradle/overlappingTaskOutputsStatsInit.gradle
Use the `java-library` plugin when calling `gradle init --type java-library`

See: gradle/performance#307

Add test for missing file dependencies matching behaviour

Test is marked as not-yet-implemented. This should work in a similar

way as it works for artifacts shown in the test case above.

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

Test Jacoco class dump dir

+review REVIEW-6418

Add comments referencing the external resource

Execute beforeTaskOutputsGenerated() before task outputs are generated

And not after.

+review REVIEW-6419

Add not yet implemented test case for local file dependency filtering

This is currently not working because file dependencies are handled

differently and the component filter is currently ignored i that case.

(see: DefaultLenientConfiguration.java#L107)

(The filter-by-attribute is also ignored there, which also

should be improved)

Mention change in release notes

+review REVIEW-6418

    • -0
    • +4
    /subprojects/docs/src/docs/release/notes.md
Rename Jacoco’s classDumpFile to classDumpDir

Deprecated the old property in favor of the new.

+review REVIEW-6418

    • -2
    • +2
    /subprojects/docs/src/docs/dsl/org.gradle.testing.jacoco.plugins.JacocoTaskExtension.xml
Handle Jacoco’s `classDumpFile` as a directory

+review REVIEW-6418

Add more test scenarios

- Filter by component type (real world use case)

- Lazy execution of transforms

move test from testkit to toolingApi

- allows better cross version checking

+review REVIEW-6414

Move ArtifactView interface to separate file

Add @incubating and @since

Remove API methods that are replaced by artefact view builder

user `Configuration.artifactView()` instead

gradle/performance#239

Remove dependency to java plugin from integration tests

gradle/performance#239

fix since tag for new TaskState

- should be 3.4 instead of 3.3

+review REVIEW-6414

Synchronize access to `concat`

The immutable attributes factory may be accessed concurrently by different threads. The odds that

`concat` is called concurrently are low but not zero, as exercised by the failure reported in

gradle/performance#310. Therefore, we need to synchronize access to `concat`. If this happens to

be too expensive, then we might need to consider:

- moving the factory to project scoped services, at the cost of higher memory usage for attributes

- use finer grained locking instead

Signed-off-by: Cedric Champeau <cedric@gradle.com>

Deal with the case when running tests where a build script is changed immediately after a build completes and the daemon which ran the build runs some other build before a third daemon runs the first build again.

Reproduce issue #1168

If you run this sequence of steps, a task may be up-to-date even though its output does not exist.

Run gradle as usual. (Gradle will execute the task, the outputs are created.)

Upgrade Gradle or delete the project .gradle.

Run gradle again. (Gradle will execute the task, the outputs are not overwritten.)

Run gradle clean. (Gradle will delete the outputs.)

Run gradle again. (Gradle will mark the task as up-to-date.) This is wrong.

Removed the guarantee that changes to output files made immediately before build are detected, as this requires always rehashing the build outputs produced during the first timestamp period of the previous build even though they are very unlikely to have changed.

Changes to input files are still detected, as these are more likely to have changed.

Deal with the case when running tests where a build script is changed immediately after a build completes and the daemon which ran the build runs some other build before returning to run the first build again.

Allow element creation via delegate provider

After considering a few different names for the delegate provider (`new`

/ `factory` / `builder` / `creator` / `creating`) I settled on

`creating`:

* it shares the same prefix with the element creation methods

(`create`) so it's arguably more discoverable

* it reads more like prose, specially when coupled with the type

tasks {

val deploy by creating(Copy::class) {

// ...

}

}

Resolves #35