[
https://issues.apache.org/jira/browse/MRESOLVER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607649#comment-17607649
]
ASF GitHub Bot commented on MRESOLVER-269:
------------------------------------------
cstamas opened a new pull request, #199:
URL: https://github.com/apache/maven-resolver/pull/199
New provided checksums implementation that uses more compact format: a
"summary" file that contains list of Artifact IDs and provided checksum per one
line.
This format is more VCS friendly, and also easier to handle then sparse
directories.
Perfomed cleanup around provided checksum sources as well, old one was in
wrong place, dropped it (as it was final class), now we have two sources:
* `file-sparse`
> Allow storage of provided checksums in file format
> --------------------------------------------------
>
> Key: MRESOLVER-269
> URL: https://issues.apache.org/jira/browse/MRESOLVER-269
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Rafael Winterhalter
> Assignee: Tamás Cservenák
> Priority: Major
> Fix For: resolver-next
>
>
> While the repository layout makes sense for storage outside of a project, it
> would be more convenient to store checksums in a single file (per algorithm)
> when keeping checksums along when storing these checksums within a project.
> This makes the storage easier to version control and avoids the overhead of
> storing a lot of files in version control what often creates some overhead.
> Ideally, Maven could support such files out of the box by shipping a provider
> for such files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
