You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/07/19 11:36:00 UTC
[jira] [Commented] (MRESOLVER-375) Several key aspects are broken in provided and trusted checksum feature
[ https://issues.apache.org/jira/browse/MRESOLVER-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744563#comment-17744563 ]
ASF GitHub Bot commented on MRESOLVER-375:
------------------------------------------
cstamas merged PR #307:
URL: https://github.com/apache/maven-resolver/pull/307
> 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
> Assignee: 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)