[
https://issues.apache.org/jira/browse/MRESOLVER-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-279:
--------------------------------------
Description:
High level changes:
* support class should meddle way less, it is here to provide some utils and
protect from future API changes
* sparse source: use `FileProcessor` both both, checksum read and write
(instead to mix in `Files.write`)
* summary source: heavily enhanced, on save it truncate or merges with
existing summary file, added change detection (prevents save when no change to
save), summary file is written out atomically, and finally file format is made
GNU Coreutils formatted, hence is usable with GNU sha1sum and alike OS tools
* introduce FileUtils, Java NIO2 based file writing utility
For both checksum sources the semantics of concurrent lookup/write is cleared
up and documented (and fixed in summary). For both purposes (lookup and
record), the source must be explicitly enabled.
Tests redone as well, and should work with any writable trusted checksum source.
was:
High level changes:
* support class should meddle way less, it is here to provide some utils and
protect from future API changes
* sparse source: use `FileProcessor` both both, checksum read and write
(instead to mix in `Files.write`)
* summary source: heavily enhanced, on save it truncate or merges with
existing summary file, added change detection (prevents save when no change to
save), summary file is written out atomically, and finally file format is made
GNU Coreutils formatted, hence is usable with GNU sha1sum and alike OS tools
* introduce FileUtils, Java NIO2 based file writing utility
For both checksum sources the semantics of concurrent lookup/write is cleared
up and documented (and fixed in summary). For lookup purposes, the source must
be explicitly enabled, while for "recording" this is not needed.
Tests redone as well, and should work with any writable trusted checksum source.
> Simplify and improve trusted checksum sources
> ---------------------------------------------
>
> Key: MRESOLVER-279
> URL: https://issues.apache.org/jira/browse/MRESOLVER-279
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.0
>
>
> High level changes:
> * support class should meddle way less, it is here to provide some utils and
> protect from future API changes
> * sparse source: use `FileProcessor` both both, checksum read and write
> (instead to mix in `Files.write`)
> * summary source: heavily enhanced, on save it truncate or merges with
> existing summary file, added change detection (prevents save when no change
> to save), summary file is written out atomically, and finally file format is
> made GNU Coreutils formatted, hence is usable with GNU sha1sum and alike OS
> tools
> * introduce FileUtils, Java NIO2 based file writing utility
> For both checksum sources the semantics of concurrent lookup/write is cleared
> up and documented (and fixed in summary). For both purposes (lookup and
> record), the source must be explicitly enabled.
> Tests redone as well, and should work with any writable trusted checksum
> source.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
