SingleArtifactResolutionResultSpec.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add tests for publishing Java platforms

    • -0
    • +4
    ./SingleArtifactResolutionResultSpec.groovy
  1. … 13 more files in changeset.
Remove the simple `shouldFail()` to force us to give explanations

    • -7
    • +4
    ./SingleArtifactResolutionResultSpec.groovy
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....`

    • -1
    • +13
    ./SingleArtifactResolutionResultSpec.groovy
  1. … 14 more files in changeset.
Migrate the Maven publish integration tests to use the same test fixtures as Ivy

This makes things much easier to understand, and explicits some expectations.

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

    • -0
    • +37
    ./SingleArtifactResolutionResultSpec.groovy
  1. … 12 more files in changeset.