[
https://issues.apache.org/jira/browse/MGPG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827427#comment-17827427
]
Harald Kuhr commented on MGPG-112:
--
Excellent, thanks! I'll try that!
> Upgrading from 3.1.0 to 3.2.0
[
https://issues.apache.org/jira/browse/MGPG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827422#comment-17827422
]
Harald Kuhr commented on MGPG-112:
--
Thanks! Great work, both on the plugin in general and locating and
[
https://issues.apache.org/jira/browse/MGPG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harald Kuhr updated MGPG-112:
-
Description:
After upgrading to Maven GPG plugin from 3.1.0 to 3.20, the Deploy step of my
projects CI
[
https://issues.apache.org/jira/browse/MGPG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harald Kuhr updated MGPG-112:
-
Environment: GitHub actions, using ubuntu-22.04 (Ubuntu 22.04 LTS) image.
Full details can be found in the
Harald Kuhr created MGPG-112:
Summary: Upgrading from 3.1.0 to 3.2.0 with no other changes
causes "gpg: signing failed: No pinentry"
Key: MGPG-112
URL: https://issues.apache.org/jira/browse/MGPG-112
[
http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88756
]
Harald Kuhr commented on MDEPLOY-48:
It's possible to upload sources via the -Dclassifier=sources switch, the
problem
