[
https://issues.apache.org/jira/browse/MRESOLVER-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-375:
--------------------------------------
Description:
Several key aspects are broken in provided and trusted checksum feature of
resolver:
* trusted checksum post processor: the checksum algorithm is not prefixed (as
documented)
* the trusted to provided adapter is defunct without MRM being configured
* the existing ProvidedChecksumsSource interface is broken, needs to be replaced
* some unused loggers and misplaced logging (ie. log may be misleading, move it
to actual file reading)
was:
Several key aspects are broken in provided and trusted checksum feature of
resolver:
* trusted checksum post processor: the checksum algorithm is not prefixed (as
documented)
* the trusted to provided adapter is defunct without MRM being configured
* the existing ProvidedChecksumsSource interface is broken, needs to be replaced
> Several key aspects are broken in provided and trusted checksum feature
> -----------------------------------------------------------------------
>
> Key: MRESOLVER-375
> URL: https://issues.apache.org/jira/browse/MRESOLVER-375
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Affects Versions: 1.9.13
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.14
>
>
> Several key aspects are broken in provided and trusted checksum feature of
> resolver:
> * trusted checksum post processor: the checksum algorithm is not prefixed (as
> documented)
> * the trusted to provided adapter is defunct without MRM being configured
> * the existing ProvidedChecksumsSource interface is broken, needs to be
> replaced
> * some unused loggers and misplaced logging (ie. log may be misleading, move
> it to actual file reading)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
