ArtifactTransformIsolationIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Write the artifact transforms for external dependencies to the configuration cache as a spec, rather than eagerly running the transform and writing the resulting files to the cache.

This means that no transforms are run eagerly. All transforms may take task outputs or other changing files as parameters and it is not easy to determine whether or not this is the case. So, for now assume that all transforms have changing parameters. A later improvement could be to eagerly run transforms for remote artifacts that do not have changing parameters.

    • -3
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 15 more files in changeset.
Write the artifact transforms for external dependencies to the configuration cache as a spec, rather than eagerly running the transform and writing the resulting files to the cache.

This means that no transforms are run eagerly. All transforms may take task outputs or other changing files as parameters and it is not easy to determine whether or not this is the case. So, for now assume that all transforms have changing parameters. A later improvement could be to eagerly run transforms for remote artifacts that do not have changing parameters.

    • -3
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 15 more files in changeset.
Write the artifact transforms for external dependencies to the configuration cache as a spec, rather than eagerly running the transform and writing the resulting files to the cache.

This means that no transforms are run eagerly. All transforms may take task outputs or other changing files as parameters and it is not easy to determine whether or not this is the case. So, for now assume that all transforms have changing parameters. A later improvement could be to eagerly run transforms for remote artifacts that do not have changing parameters.

    • -3
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 23 more files in changeset.
Attach a reason to each `@ToBeFixForInstantExecution` annotation attached to artifact transform functional tests, and also rework a few tests to use configuration cache friendly APIs.

    • -15
    • +15
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 7 more files in changeset.
Attach a reason to each `@ToBeFixForInstantExecution` annotation attached to artifact transform functional tests, and also rework a few tests to use configuration cache friendly APIs.

    • -15
    • +15
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 7 more files in changeset.
Attach a reason to each `@ToBeFixForInstantExecution` annotation attached to artifact transform functional tests, and also rework a few tests to use configuration cache friendly APIs.

    • -15
    • +15
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 7 more files in changeset.
Attach a reason to each `@ToBeFixForInstantExecution` annotation attached to artifact transform functional tests, and also rework a few tests to use configuration cache friendly APIs.

    • -15
    • +15
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 7 more files in changeset.
Fix ArtifactTransformIsolationIntegrationTest for instant execution

to not hold a Configuration as a task field

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

    • -8
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
Add @ToBeFixedForInstantExecution to ArtifactTransformIsolationIntegrationTest

because of the GenerateGraphTask in ResolveTestFixture that has a Configuration field

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

    • -0
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -2
    • +2
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +2
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 93 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +2
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 93 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +2
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 93 more files in changeset.
Accept more deprecation warnings

For tests testing the old API

    • -0
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 2 more files in changeset.
Accept more deprecation warnings

For tests testing the old API

    • -0
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 2 more files in changeset.
Accept more deprecation warnings

For tests testing the old API

    • -0
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 2 more files in changeset.
Accept more deprecation warnings

For tests testing the old API

    • -0
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 2 more files in changeset.
Migrate more test to using the new API

    • -0
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 12 more files in changeset.
Migrate more test to using the new API

    • -0
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 12 more files in changeset.
WIP

    • -0
    • +1
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 12 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.

    • -6
    • +6
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 17 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.

    • -6
    • +6
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 17 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.

    • -6
    • +6
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 17 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.

    • -6
    • +6
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 17 more files in changeset.
Do not drop variant attributes for 'traditional' 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.

    • -6
    • +6
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 27 more files in changeset.
Deprecate using `File` as InputArtifact (#8935)

Only Provider<FileSystemLocation> should be used as input artifact going forward.

    • -1
    • +2
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 12 more files in changeset.
Deprecate using `File` as InputArtifact (#8935)

Only Provider<FileSystemLocation> should be used as input artifact going forward.

    • -1
    • +2
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 12 more files in changeset.
Emit deprecation warning

    • -1
    • +2
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 12 more files in changeset.
Use inner Parameters class

for transform parameters.

    • -6
    • +6
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 7 more files in changeset.
Add TransformAction.getParameters

So the implementors of `TransformAction` don't need to add the method.

    • -5
    • +0
    ./ArtifactTransformIsolationIntegrationTest.groovy
  1. … 10 more files in changeset.