[
https://issues.apache.org/jira/browse/MRESOLVER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611146#comment-17611146
]
ASF GitHub Bot commented on MRESOLVER-269:
------------------------------------------
michael-o commented on PR #199:
URL: https://github.com/apache/maven-resolver/pull/199#issuecomment-1262576217
> > * Since the `LocalPathComposer` is used throughout the docs of the
sources should mention that this substructure is also reflected in `.checksums/`
>
> The javadoc of sparse source says:
>
> ```
> * Sparse file {@link FileTrustedChecksumsSourceSupport} implementation
that use specified directory as base
> * directory, where it expects artifacts checksums on standard Maven2
"local" layout. This implementation uses Artifact
> * coordinates solely to form path from basedir, pretty much as Maven
local repository does.
> ```
I don't see how this answers my question... ?!!
> > * As for the file-compact. I like the idea. Does it make sense to reuse
rather a well-known format like BSD checksum file? See also
[nicoulaj/checksum-maven-plugin#127](https://github.com/nicoulaj/checksum-maven-plugin/issues/127)
>
> IMHO no, as BSD checksum file contains filename, here, we operate with
ArtifactId ("file format is artifact ID and checksum separated by space per
line"), see
https://github.com/apache/maven-resolver/blob/master/maven-resolver-util/src/main/java/org/eclipse/aether/util/artifact/ArtifactIdUtils.java#L45
hm...we basically use our current format, but compile multiple files and key
them by artifact id. Agree.
> Allow more compact storage of provided checksums
> ------------------------------------------------
>
> 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)
