Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Prevent multiple build operation notification listeners.

The notification bridge has to do some work to translate from raw operation events to notifications.

Therefore, each listener introduces overhead.

We could use a broadcaster to get around this, but that incurs performance penalties in reflection and serialization that is unnecessary to pay for this case.

Include parent operation IDs in notifications.

The parent ID of a notification is the ID of the nearest operation that

also resulted in a notification.

Recompile everything whenever jars are reordered

This bugfix makes sure that we recompile everything whenever order of classpath changed, or mutation of the classpath was detected. The reason

is that the order on classpath matters, because a class can be provided in different jars, with a different ABI. For now, we

don't track precisely, when a class is compiled, _from which jar_ is used to be compiled against. This means that if the order

changes, we cannot determine precisely what needs to be recompiled. Considering that re-ordering, or additions/removals on

classpath should not be frequent (updates are still incremental), we recompile everything.

Pull test up in the hierarchy, to test both class directories and jars

Renamed a class.

Removed now pointless intermediate object.

Generate less garbage while collecting the results of traversing the dependency graph. Specifically, snapshot each `ArtifactSet` prior to adding it to the id -> `ArtifactSet` map in the results, instead of collecting the original `ArtifactSet` instances in a temporary map and then later making a copy containing the snapshots.

Retain less stuff in the resolution results for a `Configuration`. Specifically, don't keep a set of the ids of the `ArtifactSet` instances in the result that may potentially be buildable (which is often all or most of them), instead wrap only those whose task dependencies should be ignored (which is often none).

Retain less stuff in the resolution results for a `Configuration`. Specifically, don't retain both the original `ArtifactSet` and the snapshot `ArtifactSet` created from it. The original is intended to be discarded once the snapshot is available.

Fix tests for changed build operations for :buildSrc

Identify the target of scripts/plugins to build scans.

  1. … 12 more files in changeset.
Fixed issue where each dependency graph node was included twice in the old dependency resolution results written to file.

Add context to build operations for nested builds

First round of review feedback

Fix test for changed task order

Fix defect in worker failure handling for completed work

Fix checkstyle

Address more comments

Improve testing

Make progress event serialization more compact

Use a single byte to indicate nullness of all optional fields

instead of writing one byte for each of them.

Add documentation for new repository (#2081)

    • -1
    • +4
    /subprojects/docs/src/docs/dsl/org.gradle.api.artifacts.dsl.RepositoryHandler.xml
    • -0
    • +10
    /subprojects/docs/src/docs/release/notes.md
    • -0
    • +15
    /subprojects/docs/src/docs/userguide/depMngmt.adoc
Add some basic functional tests asserting task output grouping

Improve error when an in-process executer is not used

Fix bad rebase where build scan services moved out of build scope

Add functional specs for build results (#2078)

* Support for functionally testing rich console output

* Fix test on Windows

* Another attempt to fix test on Windows

* Continue to use validation of deprecation messages

* Use regex to avoid issues with comparing String with OS-specific control characters

* Add functional tests for build results

* Fix tests now that we're validating output

v0.9.0 release notes

    • -0
    • +169
    /doc/release-notes/0.9.0.md
Merge pull request #2064 from gradle/gh/taskplan/buffered-unlocks

Avoid notifying lock waiters when we roll back locks

Address code review comments

Sort task action hashes better

So the classname and the classloader hash show up next to each other

in the build scan.

+review REVIEW-6539

    • -2
    • +2
    /gradle/taskCacheBuildScanUserData.gradle
Refine samples/README.md

Add recently added samples

Update IntelliJ/Kotlin version numbers