DirectoryOutputArtifactIntegrationTest.groovy

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Let dependency-management tests not use deprecated configurations

    • -4
    • +4
    ./DirectoryOutputArtifactIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -4
    • +4
    ./DirectoryOutputArtifactIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -4
    • +4
    ./DirectoryOutputArtifactIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -4
    • +4
    ./DirectoryOutputArtifactIntegrationTest.groovy
  1. … 27 more files in changeset.
On CI redirect jcenter queries to local repo for integration tests

    • -6
    • +6
    ./DirectoryOutputArtifactIntegrationTest.groovy
  1. … 51 more files in changeset.
Move directory publish integration tests into `ivy` and `maven` subprojects

    • -64
    • +0
    ./DirectoryOutputArtifactIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix NPE when publishing an artifact without extension

While not being 100% related to the story which allows having a class directory as

a publish artifact, this commit fixes 2 `NullPointerException` that occur whenever

a published artifact doesn't have an extension (which is often the case for directories).

The first case is when a file without extension is published, which triggered the error

in `IvyXmlModuleDescriptorWriter#printPublications`. The second one is a bug in the

comparator for resolved configurations. In that case, even if a directory cannot be

published, trying to access the resolved configuration could trigger a NPE.

See: gradle/performance#84

    • -0
    • +35
    ./DirectoryOutputArtifactIntegrationTest.groovy
  1. … 3 more files in changeset.
Add test case to make sure transitive dependencies are used

This commit adds a test case to show that if a configuration has transitive dependencies, they

are used when a publish artifact is a directory.

See: gradle/performance#84

    • -4
    • +60
    ./DirectoryOutputArtifactIntegrationTest.groovy
Add test case to make sure we fail gracefully if trying to publish a directory

See: gradle/performance#84

    • -0
    • +68
    ./DirectoryOutputArtifactIntegrationTest.groovy
  1. … 1 more file in changeset.
Add a comment about the case for intra-project configuration dependencies

See: gradle/performance#84

    • -0
    • +3
    ./DirectoryOutputArtifactIntegrationTest.groovy
Add test case showing that we can depend on the output of a `JavaCompile` task

See: gradle/performance#84

    • -0
    • +36
    ./DirectoryOutputArtifactIntegrationTest.groovy
Fix the intra-project dependencies test cases

The fact that an artifact of a configuration doesn't belong to the list of files when

calling `configuration.getFiles()` is intentional. As such, we need to change the test

cases to define two configurations, one depending on the other.

One test case now passes, the second is still failing.

See: gradle/performance#84

    • -6
    • +28
    ./DirectoryOutputArtifactIntegrationTest.groovy
First integration tests for allowing a directory as a configuration artifact

See: gradle/performance#84

    • -0
    • +159
    ./DirectoryOutputArtifactIntegrationTest.groovy