Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix issue with properties object not being isolatable

Extract fixtures for android-instant-execution tests

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

Rename cleanTemplates to cleanRemoteProjects for clarity

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

Only do maven artifact discovery for variants that require it

Only do maven artifact discovery for variants that require it

Only do maven artifact discovery for variants that require it

Only do maven artifact discovery for variants that require it

Only do maven artifact discovery for variants that require it

Only do maven artifact discovery for variants that require it

Only do maven artifact discovery for variants that require it

Let resolved variants remember if they were derived

Let resolved variants remember if they were derived

Let resolved variants remember if they were derived

Let resolved variants remember if they were derived

Let resolved variants remember if they were derived

Let resolved variants remember if they were derived

Let resolved variants remember if they were derived

Deduplicate sign task inputs

Multiple inputs can be defined that point at the same file.

Integration test Santa Tracker with Instant Execution

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

Integration test Santa Tracker with Instant Execution

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

Integration test Santa Tracker with Instant Execution

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

Refine InstantExecutionAndroidIntegrationTest

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

Fix flaky predicate

Align implementations of artifact identifier display names

DefaultModuleComponentArtifactIdentifier now behaves similar as

ComponentFileArtifactIdentifier (showing the full actual file name).

This means that the artifact name used during reporting now

contains the version at the usual position in the file name.

This way it shows the actual file name for artifacts originating

from pom-only maven repositories (except snapshots, which show the

SNAPSHOT placeholder) and ivy repositories with default pattern.

The motivation for this alignment is to get the same representation for

the same file, independent of whether it was sourced from traditional

or Gradle module metadata.

  1. … 18 more files in changeset.
Align implementations of 'getDisplayName()'

DefaultModuleComponentArtifactIdentifier now behaves similar as

ComponentFileArtifactIdentifier (showing the full actual file name)

Align implementations of artifact identifier display names

DefaultModuleComponentArtifactIdentifier now behaves similar as

ComponentFileArtifactIdentifier (showing the full actual file name).

This means that the artifact name used during reporting now

contains the version at the usual position in the file name.

This way it shows the actual file name for artifacts originating

from pom-only maven repositories (except snapshots, which show the

SNAPSHOT placeholder) and ivy repositories with default pattern.

The motivation for this alignment is to get the same representation for

the same file, independent of whether it was sourced from traditional

or Gradle module metadata.

  1. … 18 more files in changeset.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

  1. … 3 more files in changeset.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

  1. … 3 more files in changeset.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

  1. … 3 more files in changeset.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

  1. … 3 more files in changeset.