[
https://issues.apache.org/jira/browse/MRESOLVER-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780296#comment-17780296
]
ASF GitHub Bot commented on MRESOLVER-295:
------------------------------------------
cstamas opened a new pull request, #352:
URL: https://github.com/apache/maven-resolver/pull/352
Shuffle it's pieces along to their final place, and deprecate the whole
class, but leave it in place, as Resolver 1.x did not deprecate it. To be
removed in 2.1 of Resolver.
---
https://issues.apache.org/jira/browse/MRESOLVER-295
> Split FileProcessor into ChecksumProcessor and PathProcessor
> ------------------------------------------------------------
>
> Key: MRESOLVER-295
> URL: https://issues.apache.org/jira/browse/MRESOLVER-295
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> 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)
