You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/10/27 10:16:00 UTC

[jira] [Updated] (MRESOLVER-295) Deprecate ChecksumUtils, split its logic in their proper place

     [ https://issues.apache.org/jira/browse/MRESOLVER-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak updated MRESOLVER-295:
--------------------------------------
    Summary: Deprecate ChecksumUtils, split its logic in their proper place  (was: Split FileProcessor into ChecksumProcessor and PathProcessor)

> Deprecate ChecksumUtils, split its logic in their proper place
> --------------------------------------------------------------
>
>                 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)