[jira] (MGPG-29) Allow options to be passed to gpg

["Dmitry Katsubo (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MGPG-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339991#comment-339991 ] 

Dmitry Katsubo commented on MGPG-29:
------------------------------------

Just a note for those who will find this issue searching for the possibility to add extra options to GPG command line:

One can probably workaround using {{~/.gnupg/gpg.conf}} (location can be overridden). In my case I had the following trouble: gpg keys are available on read-only mount, thus gpg was failing:

{code}
[INFO] --- maven-gpg-plugin:1.4:sign (default-cli) @ jaxb-xew-plugin ---
gpg: failed to create temporary file `/mount/gpg/.#lk0x7f4cd1f1fe80.localhost.284': Permission denied
gpg: fatal: can't create lock for `/mount/gpg/trustdb.gpg'
{code}

Just create {{gpg.conf}} with option {{lock-never}} and here we are.
                
> Allow options to be passed to gpg
> ---------------------------------
>
>                 Key: MGPG-29
>                 URL: https://jira.codehaus.org/browse/MGPG-29
>             Project: Maven GPG Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.1
>            Reporter: SebbASF
>            Assignee: Benjamin Bentmann
>
> It would sometimes be useful to be able to pass additional command-line options to the gpg executable.
> For example, if the secret key is stored on a removable medium the --secret-key option is needed.
> Changing the home directory to the removable medium can cause problems with the gpg2 agent.
> There may be other options that are needed on occasion.

--
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