Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Only replace -SNAPSHOT in the URLs, not names

Only replace -SNAPSHOT in the URLs, not names

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.

  1. … 33 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.

  1. … 33 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

...

  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.

  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.

  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.

  1. … 2 more files 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.

  1. … 1 more file in changeset.
Preserve all warnings of type 'variant unsupported'

  1. … 2 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

  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

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

  1. … 10 more files 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

  1. … 4 more files 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

  1. … 4 more files 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

  1. … 4 more files 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

  1. … 4 more files in changeset.
Avoid more deprecated APIs

  1. … 43 more files in changeset.
Avoid more deprecated APIs

  1. … 34 more files in changeset.
Avoid more deprecated APIs

  1. … 34 more files in changeset.
Avoid more deprecated APIs

  1. … 28 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

  1. … 63 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

  1. … 56 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

  1. … 59 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

  1. … 62 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

  1. … 60 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

  1. … 60 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

  1. … 63 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

  1. … 63 more files in changeset.
De-incubate latest dependency management APIs for 6.0 (#10886)

These are APIs that complete features which are fully implemented and

de-incubated in Gradle 6.

  1. … 8 more files in changeset.
De-incubate latest dependency management APIs for 6.0

These are APIs that complete features which are fully implemented and

de-incubated in Gradle 6.

  1. … 8 more files in changeset.