[
https://issues.apache.org/jira/browse/MRESOLVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818992#comment-17818992
]
ASF GitHub Bot commented on MRESOLVER-301:
------------------------------------------
cstamas commented on PR #432:
URL: https://github.com/apache/maven-resolver/pull/432#issuecomment-1955073321
Q1: checksums: they are _tightly coupled_ into "basic connector".
Historically, "connector" was the transport abstraction, but later "connector +
transport" was introduced, and connector deals with checksums ONLY. Original
issue was "deal with signatures as with checksums" but this is a no-go, as
connector is (theoretically) swappable, while true, we have only "basic"
connector and no other implementation. IMHO, we should eventually remove the
abstraction from connector and accept that "basic" is THE connector we use.
Q2: First, it is an extension, yes. Second, I see no problem with resolver
signing, as to me, it seems like "natural fit". If you think about, signer
plugins usually do something and "attach" the result. Am fine with both, and as
far I am concerned, the two can coexists even (maybe add some logic to signer
to remain dormant if signatures discovered).
> Artifact Generators
> -------------------
>
> Key: MRESOLVER-301
> URL: https://issues.apache.org/jira/browse/MRESOLVER-301
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> Resolver should provide extension point for "generators". Typical use case
> for these are for example "signing" of artifacts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
