You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2019/01/17 23:11:00 UTC

[jira] [Updated] (MGPG-44) gpg:sign does not handle non-Default outputDirectory correctly

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

Robert Scholte updated MGPG-44:
-------------------------------
    Labels: up-for-grabs  (was: )

> gpg:sign does not handle non-Default outputDirectory correctly
> --------------------------------------------------------------
>
>                 Key: MGPG-44
>                 URL: https://issues.apache.org/jira/browse/MGPG-44
>             Project: Maven GPG Plugin
>          Issue Type: Bug
>            Reporter: Sebb
>            Priority: Major
>              Labels: up-for-grabs
>
> The command:
> mvn verify assembly:single gpg:sign
> works fine; it creates the assemblies under target and adds the sigs to target.
> However, if the assembly plugin outputDirectory parameter is used to change the location of the assemblies - e.g. to target/tarballs - the sigs are still created, but they are left in the directory target/gpg/target/tarballs instead of being moved alongside the assemblies.
> It looks like the plugin is prefixing target/ on the ascDirectory when it should not, because defining ascDirectory=. fixes the issue



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)