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

["Maarten Mulders (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MGPG-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421984#comment-17421984 ] 

Maarten Mulders commented on MGPG-44:
-------------------------------------

Fixed with [fc7e88b|https://github.com/apache/maven-gpg-plugin/commit/fc7e88bdcc0f6f98261e36d232d4edb8e05a7f15].

> 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
>            Assignee: Maarten Mulders
>            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
(v8.3.4#803005)