IvyPublishResolvedVersionsJavaIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 10 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 10 more files in changeset.
Add test coverage for previously broken ivy publishing scnearios

    • -0
    • +35
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 1 more file in changeset.
Add test coverage for previously broken ivy publishing scnearios

    • -0
    • +36
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 1 more file in changeset.
Clean up IvyPublication and publish more information to ivy.xml metadata

This cleans up the implementation of `populateFromComponent()` and

introduces the following changes that publish information which

was lossy before:

- Artifacts are now added to all configurations they belong to and

not just the first found

- Dependencies are now added for all configurations they belong to,

with the corresponding mapping and version, and

not just for the first found

- For a Java library, this means the 'runtime' now represents the full

runtime variant of the library (before, only 'default' represented

that)

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 15 more files in changeset.
Clean up IvyPublication and publish more information to ivy.xml metadata

This cleans up the implementation of `populateFromComponent()` and

introduces the following changes that publish information which

was lossy before:

- Artifacts are now added to all configurations they belong to and

not just the first found

- Dependencies are now added for all configurations they belong to,

with the corresponding mapping and version, and

not just for the first found

- For a Java library, this means the 'runtime' now represents the full

runtime variant of the library (before, only 'default' represented

that)

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 10 more files in changeset.
Clean up IvyPublication and publish more information to ivy.xml metadata

This cleans up the implementation of `populateFromComponent()` and

introduces the following changes that publish information which

was lossy before:

- Artifacts are now added to all configurations they belong to and

not just the first found

- Dependencies are now added for all configurations they belong to,

with the corresponding mapping and version, and

not just for the first found

- For a Java library, this means the 'runtime' now represents the full

runtime variant of the library (before, only 'default' represented

that)

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 14 more files in changeset.
Adjust test fixtures and test to ivy behavior changes

    • -3
    • +3
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 38 more files in changeset.
Fixes

    • -3
    • +3
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 29 more files in changeset.
Fixes

    • -3
    • +3
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 31 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 43 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 16 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 16 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 16 more files in changeset.
Fix resolved versions of substituted dependencies

This commit fixes an inconsistency when publishing resolved

versions of a component. If that component happens to be

substituted, which would be strange for a first level dependency

but nevertheless possible, then we wouldn't find the target

module in the resolution result, and the outcome would be that

POM/IVY/Gradle Module metadata files would all have an empty

version for a substituted dependency.

With the change, we will now also look for dependencies in

the resolution result, and if one matches the original dependency

coordinates, then we use its resolved component as the result.

This allows us to _substitute_ the result with complete coordinates

in the metadata files.

Fixes nebula-plugins/gradle-nebula-integration#62

    • -0
    • +126
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 12 more files in changeset.
Fix resolved versions of substituted dependencies

This commit fixes an inconsistency when publishing resolved

versions of a component. If that component happens to be

substituted, which would be strange for a first level dependency

but nevertheless possible, then we wouldn't find the target

module in the resolution result, and the outcome would be that

POM/IVY/Gradle Module metadata files would all have an empty

version for a substituted dependency.

With the change, we will now also look for dependencies in

the resolution result, and if one matches the original dependency

coordinates, then we use its resolved component as the result.

This allows us to _substitute_ the result with complete coordinates

in the metadata files.

Fixes nebula-plugins/gradle-nebula-integration#62

    • -0
    • +126
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 12 more files in changeset.
Fix resolved versions of substituted dependencies

This commit fixes an inconsistency when publishing resolved

versions of a component. If that component happens to be

substituted, which would be strange for a first level dependency

but nevertheless possible, then we wouldn't find the target

module in the resolution result, and the outcome would be that

POM/IVY/Gradle Module metadata files would all have an empty

version for a substituted dependency.

With the change, we will now also look for dependencies in

the resolution result, and if one matches the original dependency

coordinates, then we use its resolved component as the result.

This allows us to _substitute_ the result with complete coordinates

in the metadata files.

Fixes nebula-plugins/gradle-nebula-integration#62

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

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 4 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 55 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 55 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 42 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 55 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 56 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 56 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 55 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 56 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 48 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 56 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 56 more files in changeset.
Publication of resolved versions for Ivy xml

While the feature was added for the Gradle metadata linked to an Ivy

publication, it was missed for the Ivy xml itself.

This commit corrects that, relying on the usage context attributes to

map the Ivy dependency to the requested resolved configuration.

Fixes #8948

    • -0
    • +23
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 11 more files in changeset.