Add a system property to disable publishing of SHA-256 #11358
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
melix
force-pushed
the
cc/dm/disable-sha256
branch
from
3a55fe2
to
f8f851d
Compare
|
Does this prevent maven-metadata.xml.sha512 as well? |
|
yes |
|
If the workaround stays for too long, we should probably replace this with an API on repository declaration to express supported checksums. |
vlsi
added a commit
to apache/jmeter
that referenced
this pull request
Nov 14, 2019
operasfantom
pushed a commit
to JetBrains/rd
that referenced
this pull request
Dec 16, 2019
korifey
pushed a commit
to JetBrains/rd
that referenced
this pull request
Dec 16, 2019
|
I added |
|
@autonomousapps seems like there was a clarification made in another issue. |
|
Maven Central actually fixed the root problem, so this isn't needed anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
-Dorg.gradle.internal.publish.checksums.insecureto the CLI ororg.gradle.internal.publish.checksums.insecure=trueto yourgradle.propertiesfileFixes #11308