[
http://jira.codehaus.org/browse/MGPG-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MGPG-34:
----------------------------------
Affects Version/s: (was: 1.2)
1.1
> Allow to define an alternative pomFile when sign (gpg:sign) the project
> artifact
> --------------------------------------------------------------------------------
>
> Key: MGPG-34
> URL: http://jira.codehaus.org/browse/MGPG-34
> Project: Maven 2.x GPG Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: Laszlo Hordos
> Attachments: maven-gpg-plugin.patch
>
>
> This small modification allow to specify an alternative pomFile to sign
> instead of the default project file. It's very useful when a custom pom file
> has been generated during the build process. I'm using a complex build
> configuration for a framework where I need to create custom pom files. I'm
> able create a release from my CI and publish it to the central repository the
> gpg:sign signs the wrong pom file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
