[MGPG-90] Signing fails with 3.0.1: "no pinentry"

• Type: Bug
• Status: In Progress
• Priority: Blocker
• Resolution: Unresolved
• Affects Version/s: 3.0.1
• Assignee: Tamas Cservenak
• Reporter: Jens Reimann
• Created: 19/Aug/22 08:32
• Updated: 15/Mar/24 08:09

Description

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.

Issue Links

• is caused by: MRELEASE-1114 Broken interaction of maven-gpg-plugin with Gpg4win Kleopatra since 3.0.0-M6
• is related to: MGPG-84 signing fails in eclipse when using gpg-agent