Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -1
    • +1
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 11 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -1
    • +1
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 9 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -1
    • +1
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 12 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -1
    • +1
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 9 more files in changeset.
Fix NPE and tests

    • -1
    • +1
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 6 more files in changeset.
Fix publication warning report

An output is no longer presented if all warnings are silenced by variant

name.

Fixes #11111

    • -15
    • +42
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 2 more files in changeset.
Fix publication warning report

An output is no longer presented if all warnings are silenced by variant

name.

Fixes #11111

    • -15
    • +15
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 2 more files in changeset.
Do not transform UrlBackedArtifactMetadata

There is no need to start accounting for Maven specifics since the

Gradle Module Metadata properly references the exact artifact to pick.

    • -2
    • +20
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 1 more file in changeset.
Do not transform UrlBackedArtifactMetadata

There is no need to start accounting for Maven specifics since the

Gradle Module Metadata properly references the exact artifact to pick.

    • -2
    • +20
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 1 more file in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -2
    • +2
    ./MavenPublishBuildOperationIntegrationTest.groovy
    • -0
    • +8
    ./MavenPublishConsoleIntegrationTest.groovy
    • -0
    • +3
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 30 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -2
    • +2
    ./MavenPublishBuildOperationIntegrationTest.groovy
    • -0
    • +8
    ./MavenPublishConsoleIntegrationTest.groovy
    • -0
    • +3
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 30 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -2
    • +2
    ./MavenPublishBuildOperationIntegrationTest.groovy
    • -0
    • +8
    ./MavenPublishConsoleIntegrationTest.groovy
    • -0
    • +3
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 30 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -2
    • +2
    ./MavenPublishBuildOperationIntegrationTest.groovy
    • -0
    • +8
    ./MavenPublishConsoleIntegrationTest.groovy
    • -0
    • +3
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 30 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -2
    • +2
    ./MavenPublishBuildOperationIntegrationTest.groovy
    • -0
    • +8
    ./MavenPublishConsoleIntegrationTest.groovy
    • -0
    • +3
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 30 more files in changeset.
Merge remote-tracking branch 'origin/release-5.6' into release

* origin/release-5.6: (53 commits)

Add missing - to CI config

Use dedicated user with token-based authentication to execute… (#11044)

Restore behavior of pom packaging changing the main artifact extension

Backport test fixture improvements from 6.0 branch

Relax flaky test expectation

Add equality check in case update() is called twice for the same input

Fix code comment

Add missing hashCode() method

Add test coverage to pin down selector sorting behavior

Track 'changing' and 'client module' information for override metadata

Fix equals() of client module

Remove duplicated 'isKeyEquals' check

Do not expect an exact number of HEAD requests

Remove unused imports

Make http server fixture's handle() thread safe

Add integration test for dependency artifacts in multiple declarations

Avoid copying an already immutable list

Use a linked hash set for dependency artifacts

Support artifacts with different names in maven module fixture

Use the first found dependency artifact for override metadata

...

    • -0
    • +19
    ./MavenPublishPomPackagingIntegTest.groovy
  1. … 2 more files in changeset.
Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

    • -8
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
    • -0
    • +8
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 1 more file in changeset.
Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

    • -8
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
    • -0
    • +8
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 1 more file in changeset.
Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

    • -8
    • +13
    ./MavenPublishCustomComponentIntegTest.groovy
    • -0
    • +10
    ./MavenPublishSnapshotIntegTest.groovy
  1. … 1 more file in changeset.
Do not warn for explicitly declared default capabilities

Default capabilities are declared explicitly in cases were a

variant has both the default and other capabilities. The default

capability however is still recognized in resolution if only

the pom is consumed. So warning that it cannot be published to pom

is misleading.

    • -0
    • +44
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 1 more file in changeset.
Tighten test expectation to expose issues

    • -2
    • +15
    ./AbstractMavenPublishJavaIntegTest.groovy
Merge remote-tracking branch 'origin/sg/60/baseplugin-deprecate' into release

* origin/sg/60/baseplugin-deprecate:

Fix santatracker performance template reference to buildClassPath

Fix smoke test with expected deprecation message

Fix Play unit test

Update samples to avoid deprecated APIs

Avoid more deprecated APIs

Avoid

Re-enable disabled test

Do not nag on deprecated archive task properties until Kotlin plugin is updated

Remove gretty plugin from sample

Support Providers in manifest attributes

Make BuildClassPath more idiomatic

Remove use of deprecated API

Update application plugin to use lambdas and use new Provider API methods

Restore old behavior of distribution plugin validation

Use Provider API in Distribution plugin too

Use lambdas and avoid use of deprecated archive APIs

Add nags for deprecated AbstractArchiveTask methods

Add replacements for BasePlugin.libsDir BasePlugin.distsDir

    • -1
    • +1
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 1 more file in changeset.
Do not define scope for dependencyManagement entries

The semantics between the configuration of a constraint in Gradle and the scope

of a declaration in dependencyManagement in Maven are fundamentally

different.

Given this, Gradle will no longer attempt to define a scope for

dependencyManagement entries when creating POM files.

The only exception is the import scope as it carries special meaning.

Fixes #10878

    • -5
    • +4
    ./AbstractMavenPublishJavaIntegTest.groovy
    • -12
    • +11
    ./MavenPublishJavaPlatformIntegTest.groovy
    • -1
    • +1
    ./MavenPublishMultiProjectIntegTest.groovy
    • -1
    • +0
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 1 more file in changeset.
Do not define scope for dependencyManagement entries

The semantics between the scope of a constraint in Gradle and the scope

of a declaration in dependencyManagement in Maven are fundamentally

different.

Given this, Gradle will no longer attempt to define a scope for

dependencyManagement entries when creating POM files.

The only exception is the import scope as it carries special meaning.

Fixes #10878

    • -5
    • +4
    ./AbstractMavenPublishJavaIntegTest.groovy
    • -12
    • +11
    ./MavenPublishJavaPlatformIntegTest.groovy
    • -1
    • +1
    ./MavenPublishMultiProjectIntegTest.groovy
    • -1
    • +0
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 1 more file in changeset.
Do not define scope for dependencyManagement entries

The semantics between the configuration of a constraint in Gradle and the scope

of a declaration in dependencyManagement in Maven are fundamentally

different.

Given this, Gradle will no longer attempt to define a scope for

dependencyManagement entries when creating POM files.

The only exception is the import scope as it carries special meaning.

Fixes #10878

    • -5
    • +4
    ./AbstractMavenPublishJavaIntegTest.groovy
    • -12
    • +11
    ./MavenPublishJavaPlatformIntegTest.groovy
    • -1
    • +1
    ./MavenPublishMultiProjectIntegTest.groovy
    • -1
    • +0
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 1 more file in changeset.
Do not define scope for dependencyManagement entries

The semantics between the configuration of a constraint in Gradle and the scope

of a declaration in dependencyManagement in Maven are fundamentally

different.

Given this, Gradle will no longer attempt to define a scope for

dependencyManagement entries when creating POM files.

The only exception is the import scope as it carries special meaning.

Fixes #10878

    • -5
    • +4
    ./AbstractMavenPublishJavaIntegTest.groovy
    • -12
    • +11
    ./MavenPublishJavaPlatformIntegTest.groovy
    • -1
    • +1
    ./MavenPublishMultiProjectIntegTest.groovy
    • -1
    • +0
    ./MavenPublishResolvedVersionsJavaIntegTest.groovy
  1. … 1 more file in changeset.