[jira] (MGPG-43) Allow signing of arbitrary artifacts
[ https://jira.codehaus.org/browse/MGPG-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SebbASF updated MGPG-43: Attachment: MGPG43-2.patch Updated patch - only create GpgSigner if there are some files to sign Allow signing of arbitrary artifacts Key: MGPG-43 URL: https://jira.codehaus.org/browse/MGPG-43 Project: Maven 2.x and 3.x GPG Plugin Issue Type: New Feature Reporter: SebbASF Attachments: MGPG43-2.patch, MGPG43.patch At present, the plugin relies on being run after the package phase, presumably so it knows which files to sign. This is fine if all the artifacts are intended for distribution via Maven repos, but there are other distribution mechanisms where signed artifacts are needed. For example, ASF releases to their mirror system. It would be useful if there was a separate goal for signing files using standard includes/excludes. Ideally this would also be integrated with the assembly plugin somehow so it could obtain the list of files from the plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MGPG-43) Allow signing of arbitrary artifacts
[ https://jira.codehaus.org/browse/MGPG-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SebbASF updated MGPG-43: Attachment: MGPG43-3.patch Fix bug in excludes handling Allow signing of arbitrary artifacts Key: MGPG-43 URL: https://jira.codehaus.org/browse/MGPG-43 Project: Maven 2.x and 3.x GPG Plugin Issue Type: New Feature Reporter: SebbASF Attachments: MGPG43-2.patch, MGPG43-3.patch, MGPG43.patch At present, the plugin relies on being run after the package phase, presumably so it knows which files to sign. This is fine if all the artifacts are intended for distribution via Maven repos, but there are other distribution mechanisms where signed artifacts are needed. For example, ASF releases to their mirror system. It would be useful if there was a separate goal for signing files using standard includes/excludes. Ideally this would also be integrated with the assembly plugin somehow so it could obtain the list of files from the plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MGPG-43) Allow signing of arbitrary artifacts
[ https://jira.codehaus.org/browse/MGPG-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SebbASF updated MGPG-43: Attachment: MGPG43.patch Sample implementation. Handles includes/excludes as part of configuration, plus -Dgpg.files for command-line use. Allow signing of arbitrary artifacts Key: MGPG-43 URL: https://jira.codehaus.org/browse/MGPG-43 Project: Maven 2.x and 3.x GPG Plugin Issue Type: New Feature Reporter: SebbASF Attachments: MGPG43.patch At present, the plugin relies on being run after the package phase, presumably so it knows which files to sign. This is fine if all the artifacts are intended for distribution via Maven repos, but there are other distribution mechanisms where signed artifacts are needed. For example, ASF releases to their mirror system. It would be useful if there was a separate goal for signing files using standard includes/excludes. Ideally this would also be integrated with the assembly plugin somehow so it could obtain the list of files from the plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MGPG-43) Allow signing of arbitrary artifacts
SebbASF created MGPG-43: --- Summary: Allow signing of arbitrary artifacts Key: MGPG-43 URL: https://jira.codehaus.org/browse/MGPG-43 Project: Maven 2.x and 3.x GPG Plugin Issue Type: New Feature Reporter: SebbASF At present, the plugin relies on being run after the package phase, presumably so it knows which files to sign. This is fine if all the artifacts are intended for distribution via Maven repos, but there are other distribution mechanisms where signed artifacts are needed. For example, ASF releases to their mirror system. It would be useful if there was a separate goal for signing files using standard includes/excludes. Ideally this would also be integrated with the assembly plugin somehow so it could obtain the list of files from the plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
