[jira] [Closed] (MGPG-34) Allow to define an alternative pomFile when sign (gpg:sign) the project artifact

["Robert Scholte (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MGPG-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MGPG-34.
------------------------------
      Assignee: Robert Scholte
    Resolution: Won't Fix

I am aware that some rewrite the pom.xml, but you would also need to change it with maven-install-plugin, maven-deploy-plugin and maybe even more.
Nowadays the flatten-maven-plugin intercepts this quite good, so that's the preferred way to solve it today.
In future releases of Maven we're already working on better solutions that work out of the box.
There's no need to implement this feature.

> Allow to define an alternative pomFile when sign (gpg:sign) the project artifact
> --------------------------------------------------------------------------------
>
>                 Key: MGPG-34
>                 URL: https://issues.apache.org/jira/browse/MGPG-34
>             Project: Maven GPG Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.1
>            Reporter: Laszlo Hordos
>            Assignee: Robert Scholte
>            Priority: Major
>              Labels: scrub-review-started
>         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 was sent by Atlassian Jira
(v8.3.4#803005)