Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Report annotation choosen when multiple annotations exist

Report annotation choosen when multiple annotations exist

Report annotation choosen when multiple annotations exist

Report annotation choosen when multiple annotations exist

Report subsecond build duration in ms

Signed-off-by: Paul Merlin <paul@gradle.com>

Day 2 - Convert to Kotlin

Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

Capture type annotations

Capture type annotations

Capture type annotations

Capture type annotations

Capture type annotations

Capture type annotations

Capture type annotations

Capture type annotations

Merge pull request #8940 from gradle/wolfs/incremental-inputs/documentation

Add documentation for InputChanges

Clarify when there are incremental changes

Clarify when there are incremental changes

Merge branch 'instant-execution/spike-one' of github.com:gradle/gradle into instant-execution/spike-one

Day 2 - extract instant execution logic into some separate classes.

Day 2 - Some more test coverage.

Day 2 - Handle `FileTree` properties with zero root dirs or multiple root dirs.

Polish release notes

    • -4
    • +12
    /subprojects/docs/src/docs/release/notes.md
Polish release notes

    • -4
    • +12
    /subprojects/docs/src/docs/release/notes.md
Introduce `:instantExecution` project

Day 2 - capture task name and type and some properties and uses these to rehydrate the task graph.

Rework configuration / variant exception messages

* For ambiguity issues, other attributes are listed before compatible

attributes.

* For incompatibility issues, incompatible attributes are listed first,

followed by other attributes.

Issue #8747