internal

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
make inner classes static where possible

Signed-off-by: Steven Crockett <crockett.j.steven@gmail.com>

    • -1
    • +1
    ./artifact/MavenArtifactNotationParserFactory.java
  1. … 42 more files in changeset.
Add a system property to disable publishing of SHA-256

This commit adds an internal system property which can be used as

a workaround whenever the remote repository doesn't accept SHA-256

and SHA-512 checksums. Gradle is fail-safe when it cannot upload

those files, however, in some situations, the remote repository may

not allow promoting the release if it finds such files. This is the

case in older repositories, or currently with Maven Central.

To disable publication of both SHA-256 and SHA-512 checksums, either:

- add `-Dorg.gradle.internal.publish.checksums.insecure` to the CLI or

- add `org.gradle.internal.publish.checksums.insecure=true` to your

`gradle.properties` file

Fixes #11308

    • -3
    • +6
    ./publisher/AbstractMavenPublisher.java
  1. … 7 more files in changeset.
Add a system property to disable publishing of SHA-256

This commit adds an internal system property which can be used as

a workaround whenever the remote repository doesn't accept SHA-256

and SHA-512 checksums. Gradle is fail-safe when it cannot upload

those files, however, in some situations, the remote repository may

not allow promoting the release if it finds such files. This is the

case in older repositories, or currently with Maven Central.

To disable publication of both SHA-256 and SHA-512 checksums, either:

- add `-Dorg.gradle.internal.publish.checksums.insecure` to the CLI or

- add `org.gradle.internal.publish.checksums.insecure=true` to your

`gradle.properties` file

Fixes #11308

    • -3
    • +6
    ./publisher/AbstractMavenPublisher.java
  1. … 6 more files in changeset.
Add a system property to disable publishing of SHA-256

This commit adds an internal system property which can be used as

a workaround whenever the remote repository doesn't accept SHA-256

and SHA-512 checksums. Gradle is fail-safe when it cannot upload

those files, however, in some situations, the remote repository may

not allow promoting the release if it finds such files. This is the

case in older repositories, or currently with Maven Central.

To disable publication of both SHA-256 and SHA-512 checksums, either:

- add `-Dorg.gradle.internal.publish.checksums.insecure` to the CLI or

- add `org.gradle.internal.publish.checksums.insecure=true` to your

`gradle.properties` file

Fixes #11308

    • -3
    • +6
    ./publisher/AbstractMavenPublisher.java
  1. … 7 more files in changeset.
Allow publication artifacts to be defined as files through providers

*Updated solution based on feedback to #11329*

This used to work in Gradle 5.5 (see #11054).

The combination of #9467 and #6775 broke this.

A builtBy dependency is added if the artifact is a TaskDependencyContainer,

which all Providers are (#9467). This dependency was silently doing

nothing in case of a plain File/String. This became an error (#6775)

because a File/String is nothing that can be resolved to a task.

We now only add a builtBy dependency, if the provider value or content is

actually produced by a task.

    • -1
    • +10
    ./artifact/MavenArtifactNotationParserFactory.java
  1. … 3 more files in changeset.
Allow publication artifacts to be defined as files through providers

*Updated solution based on feedback to #11329*

This used to work in Gradle 5.5 (see #11054).

The combination of #9467 and #6775 broke this.

A builtBy dependency is added if the artifact is a TaskDependencyContainer,

which all Providers are (#9467). This dependency was silently doing

nothing in case of a plain File/String. This became an error (#6775)

because a File/String is nothing that can be resolved to a task.

We now only add a builtBy dependency, if the provider value or content is

actually produced by a task.

    • -1
    • +10
    ./artifact/MavenArtifactNotationParserFactory.java
  1. … 3 more files in changeset.
Revert "Allow publication artifacts to be defined as files through providers (#11329)"

This reverts commit a4b79f33fee015bb5faded27426369ad54bae8dd.

    • -10
    • +1
    ./artifact/MavenArtifactNotationParserFactory.java
  1. … 3 more files in changeset.
Allow publication artifacts to be defined as files through providers (#11329)

This used to work in Gradle 5.5 (see #11054).

The combination of #9467 and #6775 broke this.

A builtBy dependency is added if the artifact is a TaskDependencyContainer,

which all Providers are (#9467). This dependency was silently doing

nothing in case of a plain File/String. This became an error (#6775)

because a File/String is nothing that can be resolved to a task.

We now only add a builtBy dependency, if the provider value or content is

actually produced by a task.

    • -1
    • +10
    ./artifact/MavenArtifactNotationParserFactory.java
  1. … 3 more files in changeset.
Allow publication artifacts to be defined as files through providers

This used to work in Gradle 5.5 (see #11054).

The combination of #9467 and #6775 broke this.

A builtBy dependency is added if the artifact is a TaskDependencyContainer,

which all Providers are (#9467). This dependency was silently doing

nothing in case of a plain File/String. This became an error (#6775)

because a File/String is nothing that can be resolved to a task.

We now only add a builtBy dependency, if the provider value or content is

actually produced by a task.

    • -1
    • +10
    ./artifact/MavenArtifactNotationParserFactory.java
  1. … 3 more files in changeset.
Always apply all Category disambiguation rules

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, other consumers

may also require all rules (see #11091)

    • -1
    • +1
    ./publication/DefaultMavenPublication.java
  1. … 6 more files in changeset.
Always apply all Category disambiguation rules

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, other consumers

may also require all rules (see #11091)

    • -1
    • +1
    ./publication/DefaultMavenPublication.java
  1. … 6 more files in changeset.
Introduce new metadata marker for Gradle 6 (#11109)

See: https://github.com/gradle/gradle/issues/11105

  1. … 14 more files in changeset.
Virtual 'enforced-platform' variant has separate capability

Such that it can be selected *in addition* to the regular platform

without causing a conflict.

See: https://github.com/gradle/gradle/issues/11091

    • -1
    • +1
    ./publication/DefaultMavenPublication.java
  1. … 10 more files in changeset.
Introduce new metadata marker for Gradle 6

See: https://github.com/gradle/gradle/issues/11105

  1. … 14 more files in changeset.
Introduce new metadata marker for Gradle 6

See: https://github.com/gradle/gradle/issues/11105

  1. … 14 more files in changeset.
Introduce new metadata marker for Gradle 6

See: https://github.com/gradle/gradle/issues/11105

  1. … 11 more files in changeset.
Only replace -SNAPSHOT in the URLs, not names

    • -1
    • +1
    ./publisher/AbstractMavenPublisher.java
Only replace -SNAPSHOT in the URLs, not names

    • -1
    • +1
    ./publisher/AbstractMavenPublisher.java
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.

    • -4
    • +17
    ./publisher/AbstractMavenPublisher.java
  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.

    • -4
    • +17
    ./publisher/AbstractMavenPublisher.java
  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.

    • -4
    • +17
    ./publisher/AbstractMavenPublisher.java
  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.

    • -4
    • +17
    ./publisher/AbstractMavenPublisher.java
  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.

    • -4
    • +17
    ./publisher/AbstractMavenPublisher.java
  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

...

    • -0
    • +2
    ./publisher/AbstractMavenPublisher.java
  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
    ./publisher/AbstractMavenPublisher.java
  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
    ./publisher/AbstractMavenPublisher.java
  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
    ./publisher/AbstractMavenPublisher.java
  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
    • +9
    ./publication/DefaultMavenPublication.java
  1. … 1 more file in changeset.
Preserve all warnings of type 'variant unsupported'

    • -1
    • +1
    ./publication/DefaultMavenPublication.java
  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
    • +35
    ./publisher/AbstractMavenPublisher.java
  1. … 10 more files in changeset.