[
https://jira.codehaus.org/browse/MGPG-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330461#comment-330461
]
Dennis Lundberg commented on MGPG-45:
-------------------------------------
It might be that the way you configure "outputDirectory" has an effect here.
The GPG Plugin a a parameter ascDirectory, which has an alias called
outputDirectory. So if you specify "-Doutputdirectory=target/tarballs" on the
command line, I think that will affect both the Assembly Plugin and the GPG
Plugin.
To isolate this, could you test by specifying the outputDirectory for the
Assembly Plugin in the pom.xml and see if it makes any difference?
> ascDirectory has no effect unless artifacts are not in target
> -------------------------------------------------------------
>
> Key: MGPG-45
> URL: https://jira.codehaus.org/browse/MGPG-45
> Project: Maven GPG Plugin
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: SebbASF
>
> Not sure if this is a documentation or code bug or both.
> The doc for gpg:sign / ascDirectory says:
> {code}
> The directory where to store signature files.
> Default: ${project.build.directory}/gpg
> {code}
> However changing this has no effect unless the artifacts are moved elsewhere
> than target (by changing assembly:outputDirectory).
> If outputDirectory is set to target/tarballs then the sig files are actually
> stored in target/gpg/target/tarballs for the default setting, rather than in
> the expected directory of target/gpg
> If ascDirectory is set to ASC then the sigs are stored in
> ASC/target/tarballs/ rather than ASC.
> If ascDirectory is set to "." then the sigs are stored in
> target/tarballs/ rather than the home directory.
> There does not seem to be any use-case for this behaviour, and if there is,
> it's not documented correctly.
--
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
