IvyPublishDescriptorCustomizationIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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)

    • -1
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.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)

    • -1
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.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)

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

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

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

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

    • -2
    • +0
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 43 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -1
    • +0
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -1
    • +0
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -1
    • +0
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 32 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 29 more files in changeset.
Remove an unnecessary `@IgnoreIf` from a bunch of tests.

    • -4
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 19 more files in changeset.
Remove an unnecessary `@IgnoreIf` from a bunch of tests.

    • -4
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 19 more files in changeset.
Remove an unnecessary `@IgnoreIf` from a bunch of tests.

    • -4
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 19 more files in changeset.
Remove an unnecessary `@IgnoreIf` from a bunch of tests.

    • -4
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 19 more files in changeset.
Change more tests.

    • -1
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 40 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -1
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 50 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -2
    • +2
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -2
    • +2
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -1
    • +1
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 50 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -2
    • +2
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 98 more files in changeset.
Fix Gradle Module Metadata disappearing

This commit fixes an issue where using `withXml` would

erase the Gradle Module Metadata marker from generated

POM or IVY files.

This is fixed by having the marker being a finalizer,

rather than an initial step.

    • -0
    • +27
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 4 more files in changeset.
Fix Gradle Module Metadata disappearing

This commit fixes an issue where using `withXml` would

erase the Gradle Module Metadata marker from generated

POM or IVY files.

This is fixed by having the marker being a finalizer,

rather than an initial step.

    • -0
    • +27
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 4 more files in changeset.
Fix Gradle Module Metadata disappearing

This commit fixes an issue where using `withXml` would

erase the Gradle Module Metadata marker from generated

POM or IVY files.

This is fixed by having the marker being a finalizer,

rather than an initial step.

    • -0
    • +27
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 4 more files in changeset.
Put DeferredConfigurable back in place

Only the warning message should have been conditional,

the old extension should still behave as deferred.

    • -2
    • +2
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 4 more files in changeset.
Add dedicated DSL to customize Ivy descriptor to ivy-publish plugin

This commit adds a type safe DSL for customizing the generated Ivy

module descriptor of an IvyPublication to the ivy-publish plugin:

descriptor {

license {

name = 'The Apache License, Version 2.0'

url = 'http://www.apache.org/licenses/LICENSE-2.0.txt'

}

author {

name = 'Jane Doe'

url = 'http://example.com/users/jane'

}

description {

text = 'A concise description of my library'

homepage = 'http://www.example.com/library'

}

}

Only interfaces are exposed as part of the public API, all of them are

prefixed with `IvyModuleDescriptor`. The exposed properties make use of

the Provider API.

In addition, the new DSL is documented in the User Guide, DSL Reference

and Release Notes.

Resolves #5193.

    • -7
    • +28
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 31 more files in changeset.
Nag users only once about stable_publishing flag

This was an oversight, it should have used the deprecation

logger, not a normal logger to print the warning.

    • -2
    • +2
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 28 more files in changeset.
Deprecate DeferredConfigurable

Remove it from the publishing plugins, as they no longer require it.

    • -3
    • +2
    ./IvyPublishDescriptorCustomizationIntegTest.groovy
  1. … 12 more files in changeset.