This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git
The following commit(s) were added to refs/heads/master by this push:
new 1edccef7 [MRESOLVER-353] Make checksums configurable per remote
repository (#290)
1edccef7 is described below
commit 1edccef7b95a93ddc94dead271acba4c3b44013d
Author: Tamas Cservenak <ta...@cservenak.net>
AuthorDate: Thu Jun 1 11:39:04 2023 +0200
[MRESOLVER-353] Make checksums configurable per remote repository (#290)
Setting can be applied per-remote repository, and this will affect
downloading and uploading of the checksums, per repository.
---
https://issues.apache.org/jira/browse/MRESOLVER-353
---
.../eclipse/aether/internal/impl/Maven2RepositoryLayoutFactory.java | 5 ++++-
src/site/markdown/configuration.md | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git
a/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/Maven2RepositoryLayoutFactory.java
b/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/Maven2RepositoryLayoutFactory.java
index 5586615a..e9a1ccd7 100644
---
a/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/Maven2RepositoryLayoutFactory.java
+++
b/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/Maven2RepositoryLayoutFactory.java
@@ -103,7 +103,10 @@ public final class Maven2RepositoryLayoutFactory
implements RepositoryLayoutFact
List<ChecksumAlgorithmFactory> checksumsAlgorithms =
checksumAlgorithmFactorySelector.selectList(
ConfigUtils.parseCommaSeparatedUniqueNames(ConfigUtils.getString(
- session, DEFAULT_CHECKSUMS_ALGORITHMS,
CONFIG_PROP_CHECKSUMS_ALGORITHMS)));
+ session,
+ DEFAULT_CHECKSUMS_ALGORITHMS,
+ CONFIG_PROP_CHECKSUMS_ALGORITHMS + "." +
repository.getId(),
+ CONFIG_PROP_CHECKSUMS_ALGORITHMS)));
// ensure uniqueness of (potentially user set) extension list
Set<String> omitChecksumsForExtensions =
Arrays.stream(ConfigUtils.getString(
diff --git a/src/site/markdown/configuration.md
b/src/site/markdown/configuration.md
index 797e8433..4e193dfb 100644
--- a/src/site/markdown/configuration.md
+++ b/src/site/markdown/configuration.md
@@ -28,7 +28,7 @@ Option | Type | Description | Default Value | Supports Repo
ID Suffix
`aether.artifactResolver.postProcessor.trustedChecksums.record` | boolean |
Makes `trustedChecksums` calculate and record checksums. | `false` | no
`aether.artifactResolver.postProcessor.trustedChecksums.snapshots` | boolean |
Enables or disables snapshot processing in `trustedChecksums` post processor. |
`false` | no
`aether.checksums.omitChecksumsForExtensions` | String | Comma-separated list
of extensions with leading dot (example `.asc`) that should have checksums
omitted. These are applied to sub-artifacts only. Note: to achieve 1.7.x
`aether.checksums.forSignature=true` behaviour, pass empty string as value for
this property. | `.asc,.sigstore` | no
-`aether.checksums.algorithms` | String | Comma-separated list of checksum
algorithms with which checksums are validated (downloaded) and generated
(uploaded). Resolver by default supports following algorithms: `MD5`, `SHA-1`,
`SHA-256` and `SHA-512`. New algorithms can be added by implementing
`ChecksumAlgorithmFactory` component. | `"SHA-1,MD5"` | no
+`aether.checksums.algorithms` | String | Comma-separated list of checksum
algorithms with which checksums are validated (downloaded) and generated
(uploaded). Resolver by default supports following algorithms: `MD5`, `SHA-1`,
`SHA-256` and `SHA-512`. New algorithms can be added by implementing
`ChecksumAlgorithmFactory` component. | `"SHA-1,MD5"` | yes
`aether.conflictResolver.verbose` | boolean | Flag controlling the conflict
resolver's verbose mode. | `false` | no
`aether.connector.basic.threads` or `maven.artifact.threads` | int | Number of
threads to use for uploading/downloading. | `5` | no
`aether.connector.basic.parallelPut` | boolean | Enables or disables parallel
PUT processing (parallel deploys) on basic connector globally or per remote
repository. When disabled, connector behaves exactly as in Maven 3.8.x did:
GETs are parallel while PUTs are sequential. | `true` | yes
