[
https://jira.codehaus.org/browse/MGPG-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276722#comment-276722
]
Jesse Glick commented on MGPG-31:
---------------------------------
In my setup the GPG passphrase is on a login-encrypted disk, just like the
Maven master password. I would rather "use an agent integrated with the OS" for
GPG as well as for all other purposes in Maven builds, but Maven does not
currently integrate with the GNOME keyring.
It is not clear that a fix is possible. {{SettingsDecryptionRequest}} hardcodes
servers and proxies; there is no extension point for other kinds of things that
might need passwords (such as the GPG plugin). The only thing I can think of is
to create a dummy {{server}} entry with a magic {{id}} like {{gpg}} and no
{{username}}.
It also does not look like there is any way to override
{{DefaultSettingsDecrypter}} e.g. in a build extension to do something like
integrate with a desktop keyring; I have asked on the dev list before about
injecting a higher-priority alternative to a standard service and been told it
was not possible.
> Integrate w/ Maven password encryption to avoid need to type passphrase
> -----------------------------------------------------------------------
>
> Key: MGPG-31
> URL: https://jira.codehaus.org/browse/MGPG-31
> Project: Maven 2.x and 3.x GPG Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Environment: JDK 6u21, Ubuntu, Maven 3.0 RC1
> Reporter: Jesse Glick
> Priority: Minor
> Labels: contributers-welcome
>
> It is cumbersome to be prompted for a passphrase during both release:prepare
> and release:perform:
> {noformat}
> [INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ nbm-maven-plugin
> ---
> GPG Passphrase: *
> {noformat}
> I already use http://maven.apache.org/guides/mini/guide-encryption.html (with
> a master password on an Ubuntu encrypted filesystem) so why do I need to type
> this pass phrase each time too?
> Not clear to me whether MGPG-30 already permits this. In any event, the
> plugin documentation does not seem to mention this as a use case.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
