MavenPomPackagingResolveIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -0
    • +1
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 81 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

    • -1
    • +0
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 42 more files in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -3
    • +3
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in various projects

removing most of @IgnoreWithInstantExecution annotations

after fixing the @FailsWithInstantExecution rule

and more ci feedback

also make @IgnoreWithInstantExecution require a reason from a fixed set

and add it to the remaining ignores

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -2
    • +1
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 126 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +4
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 93 more files in changeset.
Align implementations of artifact identifier display names

DefaultModuleComponentArtifactIdentifier now behaves similar as

ComponentFileArtifactIdentifier (showing the full actual file name).

This means that the artifact name used during reporting now

contains the version at the usual position in the file name.

This way it shows the actual file name for artifacts originating

from pom-only maven repositories (except snapshots, which show the

SNAPSHOT placeholder) and ivy repositories with default pattern.

The motivation for this alignment is to get the same representation for

the same file, independent of whether it was sourced from traditional

or Gradle module metadata.

    • -1
    • +1
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 32 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -1
    • +0
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 95 more files in changeset.
Create directories when registering outputs via the runtime API, too (#2929)

Previously we were creating output directories only for outputs registered via task property annotations.

    • -2
    • +2
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 32 more files in changeset.
Merge two integration tests for https://github.com/gradle/gradle/issues/1789

    • -23
    • +0
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 1 more file in changeset.
Ignore artifact when relocation exists in pom

This fixes https://github.com/gradle/gradle/issues/1789

When <relocation> element exists in pom, both original artifact

(if it exists) and relocated artifact will be downloaded, which causes

package conflict. For example, org.apache.commons:commons-io:1.3.2 is

relocated to commons-io:commons-io:1.3.2, if a project depends on

org.apache.commons:commons-io:1.3.2 and commons-io:commons-io:2.4, the

two artifacts will both exist in resolved classpath.

(See MavenPomPackagingResolveIntegrationTest.groovy provided in this

commit) This fix checks if relocation exists in pom and ignore its

artifact if necessary. This problem is first introduced in Gradle 2.0.

An integration test is provide to justify the fix.

In addition, an unnecessary artifact retrieval in test and a redundant

System.out.println("") is removed.

    • -0
    • +23
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Make `MavenMetadataLoader` use `CacheAwareExternalResourceAccessor`

This allows caching the calls to get `maven-metadata.xml`, and, since we now coordinate access to remote

resources through `CacheAwareExternalResourceAccessor`, reduce the number of remote calls in case several

projects are resolved in parallel: metadata loader honors the contract of not downloading the same

resource (`maven-metadata.xml`) concurrently.

    • -2
    • +2
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 21 more files in changeset.
Added some more test coverage for handling of maven modules with packaging other than 'jar'.

    • -26
    • +1
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 1 more file in changeset.
Allow specifying of classifier in test maven module dependency

    • -1
    • +1
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 6 more files in changeset.
Update test for changes to testing infrastructure API

    • -1
    • +2
    ./MavenPomPackagingResolveIntegrationTest.groovy
Tweaked 'could not download artifact' and 'could not find artifact' error messages.

    • -1
    • +2
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 13 more files in changeset.
Renamed subprojects/core-impl to subprojects/dependency-management.

    • -0
    • +359
    ./MavenPomPackagingResolveIntegrationTest.groovy
  1. … 1384 more files in changeset.