[
https://issues.apache.org/jira/browse/MRESOLVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820443#comment-17820443
]
ASF GitHub Bot commented on MRESOLVER-301:
------------------------------------------
gnodet commented on PR #432:
URL: https://github.com/apache/maven-resolver/pull/432#issuecomment-1962863211
> So to recap, what I tried to explain to Slawek. This PR:
>
> * defines `Artifact Generator` SPI (there may be multiple of those present
in system)
> * defines `Signer Artifact Generator` that is one provider for SPI, that
defines Signer API (there may be multiple of those present in system)
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.
> * implements GpgSigner that is one Signer implementation provided out of
the box
>
> Naturally, as generators are ordered, signer generator is expected to be
"among last" and sign not only artifacts in request (install/deploy) but also
"so far generated artifacts" (if they are relevant).
> 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)
