[ https://issues.apache.org/jira/browse/MGPG-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999149#comment-16999149 ]
Elliotte Rusty Harold commented on MGPG-45: ------------------------------------------- seems worth investigating > ascDirectory has no effect unless artifacts are not in target > ------------------------------------------------------------- > > Key: MGPG-45 > URL: https://issues.apache.org/jira/browse/MGPG-45 > Project: Maven GPG Plugin > Issue Type: Bug > Affects Versions: 1.4 > Reporter: Sebb > Priority: Major > > 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 was sent by Atlassian Jira (v8.3.4#803005)