[
http://jira.codehaus.org/browse/MGPG-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237423#action_237423
]
Jesse Glick commented on MGPG-31:
---------------------------------
Seems to work to use
http://lists.gnupg.org/pipermail/gnupg-users/2003-April/017623.html to remove
the passphrase from secring.gpg, move this file to an encrypted drive with a
symlink from the original location, then add
{noformat}
<profile>
<id>gpg</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<gpg.passphrase/>
</properties>
</profile>
{noformat}
to settings.xml. But it would be nicer to have the Maven password encryption
handle this.
> Integrate w/ Maven password encryption to avoid need to type passphrase
> -----------------------------------------------------------------------
>
> Key: MGPG-31
> URL: http://jira.codehaus.org/browse/MGPG-31
> Project: Maven 2.x GPG Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Environment: JDK 6u21, Ubuntu, Maven 3.0 RC1
> Reporter: Jesse Glick
> Priority: Minor
>
> 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.
-
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
