[MRESOLVER-279] Simplify and improve trusted checksum sources

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Component/s: Resolver
• Assignee: Tamas Cservenak
• Reporter: Tamas Cservenak
• Created: 18/Oct/22 08:57
• Updated: 25/Oct/22 20:07
• Resolved: 25/Oct/22 20:07

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 or write), the source must be explicitly enabled.

Tests redone as well, and should work with any writable trusted checksum source.

---

Issue Links

• is related to: MRESOLVER-275 Introduce trusted checksums source
• is related to: MRESOLVER-269 Allow more compact storage of provided checksums
• links to: GitHub Pull Request #203