Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Treat single version ranges as "required"

This commit changes the way Gradle handles single version

ranges to treat them like Maven does: they are effectively

"exact" version selectors (not strictly).

Fixes #11185

    • -1
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 4 more files in changeset.
Treat single version ranges as "required"

This commit changes the way Gradle handles single version

ranges to treat them like Maven does: they are effectively

"exact" version selectors (not strictly).

Fixes #11185

    • -1
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 6 more files in changeset.
Treat single version ranges as "required"

This commit changes the way Gradle handles single version

ranges to treat them like Maven does: they are effectively

"exact" version selectors (not strictly).

Fixes #11185

    • -1
    • +1
    ./MavenVersionRangeResolveIntegrationTest.groovy
  1. … 6 more files in changeset.
Catch up with master

    • -6
    • +17
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 415 more files in changeset.
Fix unique snapshot consumption with GMM

Fixes #11639

    • -6
    • +17
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix unique snapshot consumption with GMM

Fixes #11639

    • -6
    • +17
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 1 more file in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -6
    • +6
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -6
    • +6
    ./MavenDynamicResolveIntegrationTest.groovy
    • -4
    • +4
    ./MavenFileRepoResolveIntegrationTest.groovy
    • -5
    • +5
    ./MavenHttpRepoResolveIntegrationTest.groovy
    • -10
    • +10
    ./MavenJvmLibraryArtifactResolutionIntegrationTest.groovy
    • -2
    • +2
    ./MavenLatestResolveIntegrationTest.groovy
    • -4
    • +4
    ./MavenLocalDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -5
    • +5
    ./MavenLocalRepoResolveIntegrationTest.groovy
    • -6
    • +6
    ./MavenModuleArtifactResolutionIntegrationTest.groovy
    • -5
    • +5
    ./MavenParentPomResolveIntegrationTest.groovy
    • -3
    • +3
    ./MavenPomPackagingResolveIntegrationTest.groovy
    • -2
    • +2
    ./MavenPomRelocationIntegrationTest.groovy
    • -2
    • +2
    ./MavenPomResolveIntegrationTest.groovy
    • -2
    • +2
    ./MavenProfileResolveIntegrationTest.groovy
    • -12
    • +12
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
  1. … 858 more files in changeset.
Merge branch 'master' into eskatos/ie/instantIntegTest-enable

    • -0
    • +30
    ./MavenLocalRepoResolveIntegrationTest.groovy
  1. … 8 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>

    • -5
    • +4
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -2
    • +1
    ./MavenJvmLibraryArtifactResolutionIntegrationTest.groovy
    • -2
    • +1
    ./MavenPomPackagingResolveIntegrationTest.groovy
    • -4
    • +3
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -7
    • +6
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 122 more files in changeset.
Add Maven local version listing test

Issue #11321

    • -0
    • +30
    ./MavenLocalRepoResolveIntegrationTest.groovy
Add Maven local version listing test

Issue #11321

    • -0
    • +30
    ./MavenLocalRepoResolveIntegrationTest.groovy
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +7
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -0
    • +6
    ./MavenDynamicResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenFileRepoResolveIntegrationTest.groovy
    • -0
    • +5
    ./MavenHttpRepoResolveIntegrationTest.groovy
    • -0
    • +11
    ./MavenJvmLibraryArtifactResolutionIntegrationTest.groovy
    • -0
    • +2
    ./MavenLatestResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenLocalDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -0
    • +5
    ./MavenLocalRepoResolveIntegrationTest.groovy
    • -0
    • +6
    ./MavenModuleArtifactResolutionIntegrationTest.groovy
    • -0
    • +5
    ./MavenParentPomResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenPomPackagingResolveIntegrationTest.groovy
    • -0
    • +2
    ./MavenPomRelocationIntegrationTest.groovy
    • -0
    • +2
    ./MavenPomResolveIntegrationTest.groovy
    • -0
    • +2
    ./MavenProfileResolveIntegrationTest.groovy
    • -0
    • +13
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
  1. … 79 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +7
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -0
    • +6
    ./MavenDynamicResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenFileRepoResolveIntegrationTest.groovy
    • -0
    • +5
    ./MavenHttpRepoResolveIntegrationTest.groovy
    • -0
    • +11
    ./MavenJvmLibraryArtifactResolutionIntegrationTest.groovy
    • -0
    • +2
    ./MavenLatestResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenLocalDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -0
    • +5
    ./MavenLocalRepoResolveIntegrationTest.groovy
    • -0
    • +6
    ./MavenModuleArtifactResolutionIntegrationTest.groovy
    • -0
    • +5
    ./MavenParentPomResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenPomPackagingResolveIntegrationTest.groovy
    • -0
    • +2
    ./MavenPomRelocationIntegrationTest.groovy
    • -0
    • +2
    ./MavenPomResolveIntegrationTest.groovy
    • -0
    • +2
    ./MavenProfileResolveIntegrationTest.groovy
    • -0
    • +13
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
  1. … 79 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +7
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -0
    • +6
    ./MavenDynamicResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenFileRepoResolveIntegrationTest.groovy
    • -0
    • +5
    ./MavenHttpRepoResolveIntegrationTest.groovy
    • -0
    • +11
    ./MavenJvmLibraryArtifactResolutionIntegrationTest.groovy
    • -0
    • +2
    ./MavenLatestResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenLocalDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -0
    • +5
    ./MavenLocalRepoResolveIntegrationTest.groovy
    • -0
    • +6
    ./MavenModuleArtifactResolutionIntegrationTest.groovy
    • -0
    • +5
    ./MavenParentPomResolveIntegrationTest.groovy
    • -0
    • +4
    ./MavenPomPackagingResolveIntegrationTest.groovy
    • -0
    • +2
    ./MavenPomRelocationIntegrationTest.groovy
    • -0
    • +2
    ./MavenPomResolveIntegrationTest.groovy
    • -0
    • +2
    ./MavenProfileResolveIntegrationTest.groovy
    • -0
    • +13
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
  1. … 79 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

    • -2
    • +91
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 10 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

Fixes #10916

    • -2
    • +91
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 7 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

Fixes #10916

    • -2
    • +91
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 7 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

    • -2
    • +91
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 10 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +6
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -0
    • +1
    ./MavenLocalRepoResolveIntegrationTest.groovy
    • -0
    • +1
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -0
    • +1
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +6
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -0
    • +1
    ./MavenLocalRepoResolveIntegrationTest.groovy
    • -0
    • +1
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -0
    • +1
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +6
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -0
    • +1
    ./MavenLocalRepoResolveIntegrationTest.groovy
    • -0
    • +1
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -0
    • +1
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +6
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -0
    • +1
    ./MavenLocalRepoResolveIntegrationTest.groovy
    • -0
    • +1
    ./MavenRemoteDependencyWithGradleMetadataResolutionIntegrationTest.groovy
    • -0
    • +1
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
Variant aware and legacy dependency setup invalid

A dependency declaration either needs to be about variant aware

dependency management with attributes and capabilities or about legacy

artifacts and configuration.

Mixing the two is now disallowed explicitly.

Issue #10532

    • -0
    • +17
    ./MavenDependencyResolveIntegrationTest.groovy
  1. … 2 more files in changeset.
Variant aware and legacy dependency setup invalid

A dependency declaration either needs to be about variant aware

dependency management with attributes and capabilities or about legacy

artifacts and configuration.

Mixing the two is now disallowed explicitly.

Issue #10532

    • -0
    • +17
    ./MavenDependencyResolveIntegrationTest.groovy
  1. … 2 more files in changeset.
Variant aware and legacy dependency setup invalid

A dependency declaration either needs to be about variant aware

dependency management with attributes and capabilities or about legacy

artifacts and configuration.

Mixing the two is now disallowed explicitly.

Issue #10532

    • -0
    • +17
    ./MavenDependencyResolveIntegrationTest.groovy
  1. … 2 more files in changeset.
Adjust test fixtures and test to ivy behavior changes

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

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

    • -6
    • +6
    ./MixedMavenAndIvyModulesIntegrationTest.groovy
  1. … 19 more files in changeset.
Fixes

    • -6
    • +6
    ./MixedMavenAndIvyModulesIntegrationTest.groovy
  1. … 31 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.

    • -2
    • +2
    ./MavenBrokenRemoteResolveIntegrationTest.groovy
    • -2
    • +2
    ./MavenDynamicResolveIntegrationTest.groovy
    • -1
    • +1
    ./MavenJvmLibraryArtifactResolutionIntegrationTest.groovy
    • -1
    • +1
    ./MavenModuleArtifactResolutionIntegrationTest.groovy
    • -1
    • +1
    ./MavenPomPackagingResolveIntegrationTest.groovy
    • -2
    • +2
    ./MavenSnapshotResolveIntegrationTest.groovy
  1. … 27 more files in changeset.