cstamas commented on PR #199:
URL: https://github.com/apache/maven-resolver/pull/199#issuecomment-1260956232
> * 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.
```
> * 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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
