[
https://issues.apache.org/jira/browse/MRESOLVER-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-295:
--------------------------------------
Description:
The FileProcessor should become obsolete.
Instead, split this component in two: ChecksumProcessor and PathProcessor.
PathProcessor should be doing what currently FileUtils are doing, but as a
component. Maybe extended with DirectoryUtils functionality? (so component can
be "enriched" by Maven for example).
ChecksumProcessor being dedicated component opens the gate to support several
formats of checksums (BSD, GNU and resolver-native are all able to read, but we
write only resolver-native format).
was:
The FileProcessor should become obsolete.
Instead, split this component in two: ChecksumProcessor and PathProcessor.
PathProcessor should be doing what currently FileUtils are doing, but as a
component.
ChecksumProcessor being dedicated component opens the gate to support several
formats of checksums (BSD, GNU and resolver-native are all able to read, but we
write only resolver-native format).
> Split FileProcessor into ChecksumProcessor and PathProcessor
> ------------------------------------------------------------
>
> Key: MRESOLVER-295
> URL: https://issues.apache.org/jira/browse/MRESOLVER-295
> Project: Maven Resolver
> Issue Type: Task
> Reporter: Tamas Cservenak
> Priority: Major
>
> The FileProcessor should become obsolete.
> Instead, split this component in two: ChecksumProcessor and PathProcessor.
> PathProcessor should be doing what currently FileUtils are doing, but as a
> component. Maybe extended with DirectoryUtils functionality? (so component
> can be "enriched" by Maven for example).
> ChecksumProcessor being dedicated component opens the gate to support several
> formats of checksums (BSD, GNU and resolver-native are all able to read, but
> we write only resolver-native format).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
