[
https://issues.apache.org/jira/browse/MRESOLVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820471#comment-17820471
]
ASF GitHub Bot commented on MRESOLVER-301:
------------------------------------------
gnodet commented on PR #432:
URL: https://github.com/apache/maven-resolver/pull/432#issuecomment-1962938412
> > Now that you put it that way, I'm not really convinced we need a Signer
SPI here. The code of the ArtifactGenerator which calls the signers is trivial,
so it seems to me that the GpgSigner could directly implement the Artifact
Generator SPI.
>
> Agreed, will simplify it more, but the question begs: "generator-signer"
module name becomes wrong, no? Should it be maybe "generator-gnupg (or gpg)"
instead?
Yes, I think that would make more sense.
> 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, 2.0.0-alpha-9
>
>
> 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)
