[jira] [Created] (MGPG-90) Signing fails with 3.0.1: "no pinentry"

["Jens Reimann (Jira)" <ji...@apache.org>]

Jens Reimann created MGPG-90:
--------------------------------

             Summary: Signing fails with 3.0.1: "no pinentry"
                 Key: MGPG-90
                 URL: https://issues.apache.org/jira/browse/MGPG-90
             Project: Maven GPG Plugin
          Issue Type: Bug
    Affects Versions: 3.0.1
            Reporter: Jens Reimann


Starting with 3.0.1 performing a maven release fails in the process of signing artifacts with the message: "gpg: no pinentry".

I do believe this is due to the fact that in non-interactive mode with a newer `gpg` version, the gpg plugin forces a "pinentry error" if no pin is provided. And the release plugin runs the gpg plugin in non-interactive mode

However, not everyone wants to store the pin in a configuration file. Assuming you have an interactive release process, you also might want an interactive pin entry.

I would suggest to allow the user to force the pin entry to interactive (not matter what the current maven context says). That way, you can keep the current behavior, but still allow a manual/interactive release process.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)