You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/07/25 18:19:32 UTC
[jira] Closed: (MGPG-29) Allow options to be passed to gpg
[ http://jira.codehaus.org/browse/MGPG-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MGPG-29.
---------------------------------
Resolution: Won't Fix
Assignee: Benjamin Bentmann
I dislike the idea of allowing arbitrary command line options to be passed in as this complicates the plugin's logic to interpret/validate the options, making it hard for future plugin versions to use non-CLI based means like a pure Java library to do the processing.
In MGPG-30, I added however the options required to support the concrete use case you mentioned here, i.e. using alternative keyrings.
> Allow options to be passed to gpg
> ---------------------------------
>
> Key: MGPG-29
> URL: http://jira.codehaus.org/browse/MGPG-29
> Project: Maven 2.x 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira