[
https://issues.apache.org/jira/browse/MGPG-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836693#comment-17836693
]
ASF GitHub Bot commented on MGPG-125:
-------------------------------------
cstamas commented on PR #95:
URL: https://github.com/apache/maven-gpg-plugin/pull/95#issuecomment-2052127538
For last build this PR:
```
[INFO] Building: sign-release-best-practices/pom.xml
[INFO] run post-build script verify.groovy
[INFO] sign-release-best-practices/pom.xml .............. SUCCESS
(4.002 s)
```
2nd build/commit:
```
[INFO] Building: sign-release-best-practices/pom.xml
[INFO] run post-build script verify.groovy
[INFO] sign-release-best-practices/pom.xml .............. SUCCESS
(3.877 s)
```
Hm, minimal... unsure what I "feel" locally. Maybe that these two ITs use
_new_ plugins (hence downoads them) while all the rest use old/ancient plugins
but some version?
> Due to default value of gpg.passphraseServerId, bestPractices=true will
> always fail
> -----------------------------------------------------------------------------------
>
> Key: MGPG-125
> URL: https://issues.apache.org/jira/browse/MGPG-125
> Project: Maven GPG Plugin
> Issue Type: Bug
> Affects Versions: 3.2.3
> Reporter: Benjamin Marwell
> Assignee: Tamas Cservenak
> Priority: Critical
> Fix For: 3.2.4
>
>
> Running gpg-plugin with best practices from the CLI, it will always fail
> since gpg.passphraseServerId does have a default value set.
> See:
> https://github.com/apache/maven-gpg-plugin/blob/master/src/main/java/org/apache/maven/plugins/gpg/AbstractGpgMojo.java#L140
> CC [~cstamas]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
