publisher

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Do not publish stale signature files

This commit fixes the publication of stale signature files:

prior to this change it was possible that a signature generated

in a previous build for a different artifact was uploaded even

if no signature was generated during the build, which would

lead to inconsistent publications.

In addition, it makes it an error to publish something which

doesn't have the main artifact created (or, at least up-to-date)

in this build. In other words, if the task which generates the

main artifact is disabled, it's an error to publish.

Other stale artifacts are going to be ignored.

Fixes #5136

  1. … 37 more files in changeset.
Do not publish stale signature files

This commit fixes the publication of stale signature files:

prior to this change it was possible that a signature generated

in a previous build for a different artifact was uploaded even

if no signature was generated during the build, which would

lead to inconsistent publications.

In addition, it makes it an error to publish something which

doesn't have the main artifact created (or, at least up-to-date)

in this build. In other words, if the task which generates the

main artifact is disabled, it's an error to publish.

Other stale artifacts are going to be ignored.

Fixes #5136

  1. … 38 more files in changeset.
Do not publish stale signature files

This commit fixes the publication of stale signature files:

prior to this change it was possible that a signature generated

in a previous build for a different artifact was uploaded even

if no signature was generated during the build, which would

lead to inconsistent publications.

In addition, it makes it an error to publish something which

doesn't have the main artifact created (or, at least up-to-date)

in this build. In other words, if the task which generates the

main artifact is disabled, it's an error to publish.

Other stale artifacts are going to be ignored.

Fixes #5136

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

  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

  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

  1. … 7 more files in changeset.
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.
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.
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.
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 change extension of published artifact based on pom packaging

We now publish the artifacts as they were defined in the build.

If the packaging and artifact extension should be aligned, this

can easily be done by adjusting the artifact extension when

building it (e.g. by utilizing jar.archiveExtension.set())

Before this change, Gradle Module Metadata was broken for artifacts

that were changed after the metadata file has been generated

(newly added 'MavenPublishPomPackagingJavaIntegTest' tests failed).

  1. … 3 more files in changeset.
Restore behavior of pom packaging changing the main artifact extension

This restores the behavior before #9445 (before 5.6) and with

that fixes #10555.

The behavior for non-jar packaging is still problematic and should

be changed for 6.0 as it leads to broken Gradle Module Metadata.

  1. … 1 more file in changeset.
Restore behavior of pom packaging changing the main artifact extension

This restores the behavior before #9445 (before 5.6) and with

that fixes #10555.

The behavior for non-jar packaging is still problematic and should

be changed for 6.0 as it leads to broken Gradle Module Metadata.

  1. … 1 more file in changeset.
Restore behavior of pom packaging changing the main artifact extension

This restores the behavior before #9445 (before 5.6) and with

that fixes #10555.

The behavior for non-jar packaging is still problematic and should

be changed for 6.0 as it leads to broken Gradle Module Metadata.

  1. … 1 more file in changeset.
Remove deprecated methods

Latest versions of org.jfrog.buildinfo:build-info-extractor-gradle no

longer use these APIs

  1. … 5 more files in changeset.
Remove deprecated methods

Latest versions of org.jfrog.buildinfo:build-info-extractor-gradle no

longer use these APIs

  1. … 5 more files in changeset.
Remove deprecated methods

Latest versions of org.jfrog.buildinfo:build-info-extractor-gradle no

longer use these APIs

  1. … 5 more files in changeset.
Remove deprecated methods

Latest versions of org.jfrog.buildinfo:build-info-extractor-gradle no

longer use these APIs

  1. … 5 more files in changeset.
Remove deprecated methods

Latest versions of org.jfrog.buildinfo:build-info-extractor-gradle no

longer use these APIs

  1. … 5 more files in changeset.
Remove deprecated methods

Latest versions of org.jfrog.buildinfo:build-info-extractor-gradle no

longer use these APIs

  1. … 5 more files in changeset.
Remove deprecated methods

Latest versions of org.jfrog.buildinfo:build-info-extractor-gradle no

longer use these APIs

  1. … 5 more files in changeset.