IvyPublishCoordinatesIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge remote-tracking branch 'origin/master-test' into release-test

    • -7
    • +3
    ./IvyPublishCoordinatesIntegTest.groovy
Merge remote-tracking branch 'origin/master-test' into release-test

    • -7
    • +3
    ./IvyPublishCoordinatesIntegTest.groovy
Merge remote-tracking branch 'origin/master-test' into release-test

    • -7
    • +3
    ./IvyPublishCoordinatesIntegTest.groovy
Turn 'multiple publications with same coordinates' error into warning

This reduces the severity of the error detection introduced in #9466.

Although this situation is technically an error that should be avoided

as it causes information loss in the published result, in some testing

scenarios builds may rely on this behavior. So instead of failing,

Gradle now prints a warning message.

    • -6
    • +6
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 2 more files in changeset.
Turn 'multiple publications with same coordinates' error into warning

This reduces the severity of the error detection introduced in #9466.

Although this situation is technically an error that should be avoided

as it causes information loss in the published result, in some testing

scenarios builds may rely on this behavior. So instead of failing,

Gradle now prints a warning message.

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

    • -7
    • +3
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 43 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

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

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

    • -7
    • +3
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 29 more files in changeset.
Add more coverage for duplicate checking with `ivy-publish`

    • -0
    • +73
    ./IvyPublishCoordinatesIntegTest.groovy
Add more coverage for duplicate checking with `ivy-publish`

    • -0
    • +73
    ./IvyPublishCoordinatesIntegTest.groovy
Add more coverage for duplicate checking with `ivy-publish`

    • -0
    • +73
    ./IvyPublishCoordinatesIntegTest.groovy
Detect duplicate publications for `ivy-publish`

    • -0
    • +43
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 7 more files in changeset.
Detect duplicate publications for `ivy-publish`

    • -0
    • +43
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 8 more files in changeset.
Detect duplicate publications for `ivy-publish`

    • -0
    • +43
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 8 more files in changeset.
Detect duplicate publications for `ivy-publish`

    • -0
    • +43
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 8 more files in changeset.
Detect duplicate publications for `ivy-publish`

    • -0
    • +43
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 8 more files in changeset.
Detect duplicate publications for `ivy-publish`

    • -0
    • +43
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 7 more files in changeset.
Detect duplicate publications for `ivy-publish`

    • -0
    • +43
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 8 more files in changeset.
Introduce `noComponentPublished()` expectation

This expectation needs to be used whenever we expect resolution failure because no component was published.

This happens with Gradle metadata only, as the only way to publish a module file is `from components....`

    • -2
    • +8
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 14 more files in changeset.
Enfore looking only for `ivy` or `gradle` metadata when doing resolution

This commit uses the `metadataSources` to make sure that when we re-resolve, we only use the expected metadata source.

This prevents some tests from accidentally passing because we resolve to Ivy after failing with Gradle.

    • -3
    • +12
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 5 more files in changeset.
Resolve published Ivy files twice, with and without Gradle metadata

This commit changes the Ivy publication tests so that we resolve the published files twice:

- once with Gradle metadata

- once without Gradle metadata

Expectations are set on both, using a single entry point (`resolveArtifacts`). This removes the

explosion of `resolveArtifact` methods.

    • -3
    • +3
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 12 more files in changeset.
Make java libraries publishable on Ivy using Gradle metadata

This commit completes Gradle metadata publishing on Ivy repositories. It adds the necessary support, and

converts several tests to the wrapping `javaLibrary` test fixture.

    • -5
    • +9
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 28 more files in changeset.
Fix Java component publishing

When we introduced the `java-library` plugin, we made sure

the published POM reflects what a downstream project in the

same build would see: `api` dependencies are exposed, `implementation`

dependencies are hidden. The legacy `compile`/`runtime` dependencies

are exposed as well for backwards compatibility.

We forgot to adjust the tests for the existing `java` plugin,

leading to a confusing difference in behavior. The `java` plugin

was still hiding the legacy `compile` and `runtime` dependencies from

consumers. This was due to a bug in the implementation of `JavaLibrary`,

which was looking for the `api` configuration instead of the `apiElements`

configuration.

    • -3
    • +3
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 24 more files in changeset.
Updated superclass for publish integration tests

    • -2
    • +0
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 15 more files in changeset.
moved all s3 related resources, fixtures, tests and integration tests into resourceS3 subproject

- required to add maven/ivy testfixtures (only compiling one class each atm)

+review REVIEW-5361

    • -0
    • +2
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 69 more files in changeset.
Integration tests for modifying publication coordinates

    • -6
    • +69
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 1 more file in changeset.
Can now explicitly set publication coordinates for a Maven or Ivy publication - Use a convention mapping to set default artifact name in ivy publication (temporary until we get lazy configuration sorted properly)

    • -0
    • +69
    ./IvyPublishCoordinatesIntegTest.groovy
  1. … 9 more files in changeset.