Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix the serialization of `ArtifactCollection` instances that contain the output of artifact transforms to the instant execution cache.

Use a similar strategy to that used to capture the contents of a `FileCollection` that contains the output of artifact transforms.

    • -13
    • +12
    ./resolve/api/ArtifactCollectionIntegrationTest.groovy
    • -68
    • +63
    ./resolve/transform/ArtifactTransformCachingIntegrationTest.groovy
  1. … 6 more files in changeset.
Fix the serialization of `ArtifactCollection` instances that contain the output of artifact transforms to the instant execution cache.

Use a similar strategy to that used to capture the contents of a `FileCollection` that contains the output of artifact transforms.

    • -13
    • +12
    ./resolve/api/ArtifactCollectionIntegrationTest.groovy
    • -68
    • +63
    ./resolve/transform/ArtifactTransformCachingIntegrationTest.groovy
  1. … 6 more files in changeset.
Make it possible to declare a group of repositories for exclusive content

This should address the case where an artifact can be found in a specific

group of repositories, not in a single one. This is for example the case

when an artifact can be found either in the 'release' or 'snapshot'

repository of a company, but not on the public repositories.

    • -0
    • +104
    ./resolve/ExclusiveRepositoryContentFilteringIntegrationTest.groovy
  1. … 3 more files in changeset.
Make it possible to declare a group of repositories for exclusive content

This should address the case where an artifact can be found in a specific

group of repositories, not in a single one. This is for example the case

when an artifact can be found either in the 'release' or 'snapshot'

repository of a company, but not on the public repositories.

    • -0
    • +104
    ./resolve/ExclusiveRepositoryContentFilteringIntegrationTest.groovy
  1. … 3 more files in changeset.
Add a way to declare exclusive content for each repository

Before this change, if a repository declared contents using

`repository.content { include "...." }`, it was required to

also declare that the _other_ repositories excluded it in

order to be mutually exclusive.

There's now an API which allows to declare exclusive content:

```

repositories {

exclusiveContent {

forRepository {

maven { url "https://my-company-repo.com" }

}

filter { includeGroup("com.mycompany") }

}

mavenCentral()

}

```

    • -0
    • +144
    ./resolve/ExclusiveRepositoryContentFilteringIntegrationTest.groovy
  1. … 6 more files in changeset.
Add a way to declare exclusive content for each repository

Before this change, if a repository declared contents using

`repository.content { include "...." }`, it was required to

also declare that the _other_ repositories excluded it in

order to be mutually exclusive.

There's now an API which allows to declare exclusive content:

```

repositories {

exclusiveContent {

forRepository {

maven { url "https://my-company-repo.com" }

}

filter { includeGroup("com.mycompany") }

}

mavenCentral()

}

```

    • -0
    • +144
    ./resolve/ExclusiveRepositoryContentFilteringIntegrationTest.groovy
  1. … 6 more files in changeset.
Add a way to declare exclusive content for each repository

Before this change, if a repository declared contents using

`repository.content { include "...." }`, it was required to

also declare that the _other_ repositories excluded it in

order to be mutually exclusive.

There's now an API which allows to declare exclusive content:

```

repositories {

exclusiveContent {

forRepository {

maven { url "https://my-company-repo.com" }

}

filter { includeGroup("com.mycompany") }

}

mavenCentral()

}

```

    • -0
    • +144
    ./resolve/ExclusiveRepositoryContentFilteringIntegrationTest.groovy
  1. … 6 more files in changeset.
Fixes for previous commit.

    • -2
    • +0
    ./resolve/transform/ArtifactTransformValuesInjectionIntegrationTest.groovy
    • -4
    • +3
    ./resolve/transform/ArtifactTransformWithDependenciesIntegrationTest.groovy
Do not fail when writing an artifact transform that takes the upstream dependencies of the artifact to the instant execution cache.

In this change, the result will be incorrect because an empty set of dependencies is passed to the transform action when it is loaded from the cache.

    • -2
    • +0
    ./resolve/transform/ArtifactTransformValuesInjectionIntegrationTest.groovy
    • -4
    • +3
    ./resolve/transform/ArtifactTransformWithDependenciesIntegrationTest.groovy
  1. … 8 more files in changeset.
Do not fail when writing an artifact transform that takes the upstream dependencies of the artifact to the instant execution cache.

In this change, the result will be incorrect because an empty set of dependencies is passed to the transform action when it is loaded from the cache.

    • -2
    • +0
    ./resolve/transform/ArtifactTransformValuesInjectionIntegrationTest.groovy
    • -4
    • +3
    ./resolve/transform/ArtifactTransformWithDependenciesIntegrationTest.groovy
  1. … 8 more files in changeset.
Fix for previous commit.

    • -2
    • +0
    ./resolve/transform/ArtifactTransformValuesInjectionIntegrationTest.groovy
    • -3
    • +0
    ./resolve/transform/ArtifactTransformWithFileInputsIntegrationTest.groovy
Fix for previous commit.

    • -1
    • +0
    ./resolve/transform/ArtifactTransformValuesInjectionIntegrationTest.groovy
    • -1
    • +0
    ./resolve/transform/ArtifactTransformWithFileInputsIntegrationTest.groovy
Serialize the parameters of an artifact transform to the instant execution cache, rather than attempting to isolate the parameters and then serializing the result.

This allows the parameters to include files and other inputs that may need to be built before they can be queried, for example when the output of some transform is used as an input parameter to another transform (which is something different to chaining of several transforms to produce an output). An implication of this change is that the artifact parameter isolation now happens every time the cache is reused, whereas previously the isolation happened once on write. This can be improved later.

    • -3
    • +0
    ./resolve/transform/ArtifactTransformValuesInjectionIntegrationTest.groovy
    • -4
    • +0
    ./resolve/transform/ArtifactTransformWithFileInputsIntegrationTest.groovy
  1. … 10 more files in changeset.
Serialize the parameters of an artifact transform to the instant execution cache, rather than attempting to isolate the parameters and then serializing the result.

This allows the parameters to include files and other inputs that may need to be built before they can be queried, for example when the output of some transform is used as an input parameter to another transform (which is something different to chaining of several transforms to produce an output). An implication of this change is that the artifact parameter isolation now happens every time the cache is reused, whereas previously the isolation happened once on write. This can be improved later.

    • -3
    • +0
    ./resolve/transform/ArtifactTransformValuesInjectionIntegrationTest.groovy
    • -4
    • +0
    ./resolve/transform/ArtifactTransformWithFileInputsIntegrationTest.groovy
  1. … 10 more files in changeset.
Treat single version ranges as "required"

This commit changes the way Gradle handles single version

ranges to treat them like Maven does: they are effectively

"exact" version selectors (not strictly).

Fixes #11185

    • -9
    • +0
    ./resolve/ivy/IvyDynamicRevisionResolveIntegrationTest.groovy
    • -1
    • +1
    ./resolve/maven/MavenVersionRangeResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Treat single version ranges as "required"

This commit changes the way Gradle handles single version

ranges to treat them like Maven does: they are effectively

"exact" version selectors (not strictly).

Fixes #11185

    • -9
    • +0
    ./resolve/ivy/IvyDynamicRevisionResolveIntegrationTest.groovy
    • -1
    • +1
    ./resolve/maven/MavenVersionRangeResolveIntegrationTest.groovy
  1. … 5 more files in changeset.
Treat single version ranges as "required"

This commit changes the way Gradle handles single version

ranges to treat them like Maven does: they are effectively

"exact" version selectors (not strictly).

Fixes #11185

    • -9
    • +0
    ./resolve/ivy/IvyDynamicRevisionResolveIntegrationTest.groovy
    • -1
    • +1
    ./resolve/maven/MavenVersionRangeResolveIntegrationTest.groovy
  1. … 5 more files in changeset.
Mark tests as failing with instant execution

    • -0
    • +1
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +1
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
Mark tests as failing with instant execution

    • -0
    • +1
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +1
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
Mark tests as failing with instant execution

    • -0
    • +1
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +1
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
Mark tests as failing with instant execution

    • -0
    • +1
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +1
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
Mark tests as failing with instant execution

    • -0
    • +1
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +1
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +72
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +35
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
  1. … 10 more files in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +72
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +35
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
  1. … 10 more files in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +71
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +35
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
  1. … 10 more files in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +72
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +35
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
  1. … 10 more files in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +71
    ./resolve/verification/DependencyVerificationIntegrityCheckIntegTest.groovy
    • -0
    • +35
    ./resolve/verification/DependencyVerificationWritingIntegTest.groovy
  1. … 10 more files in changeset.
Add ignore key test coverage and bump wrapper

    • -0
    • +75
    ./resolve/verification/DependencyVerificationSignatureCheckIntegTest.groovy
  1. … 1 more file in changeset.
Add ignore key test coverage and bump wrapper

    • -0
    • +75
    ./resolve/verification/DependencyVerificationSignatureCheckIntegTest.groovy
  1. … 1 more file in changeset.
More test coverage + fixes for tests.

    • -1
    • +40
    ./resolve/transform/ArtifactTransformValuesInjectionIntegrationTest.groovy
  1. … 4 more files in changeset.