[jira] [Updated] (MGPG-113) Upgrading from 3.1.0 to 3.2.1 with no other changes causes "gpg:sign-and-deploy-file" failed: 401 Unauthorized

2024-03-22 Thread Tim Tim (Jira)
[ https://issues.apache.org/jira/browse/MGPG-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Tim updated MGPG-113: - Summary: Upgrading from 3.1.0 to 3.2.1 with no other changes causes "gpg:sign-and-deploy-file" failed: 401 Unauthor

[jira] [Updated] (MGPG-113) Upgrading from 3.1.0 to 3.2.1 with no other changes causes "gpg:sign-and-deploy-file failed: 401 Unauthorized

2024-03-21 Thread Tim Tim (Jira)
[ https://issues.apache.org/jira/browse/MGPG-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Tim updated MGPG-113: - Description: After upgrading to Maven GPG plugin from 3.1.0 to 3.2.0/3.2.1, the deploy command "{*}gpg:sign-and-de

[jira] [Created] (MGPG-113) Upgrading from 3.1.0 to 3.2.1 with no other changes causes "gpg:sign-and-deploy-file failed: 401 Unauthorized

2024-03-21 Thread Tim Tim (Jira)
Tim Tim created MGPG-113: Summary: Upgrading from 3.1.0 to 3.2.1 with no other changes causes "gpg:sign-and-deploy-file failed: 401 Unauthorized Key: MGPG-113 URL: https://issues.apache.org/jira/browse/MGPG-113