You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Fabrizio Giudici (JIRA)" <ji...@codehaus.org> on 2010/02/28 21:59:55 UTC

[jira] Commented: (MGPG-17) password is specified, but still promting

    [ http://jira.codehaus.org/browse/MGPG-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211952#action_211952 ] 

Fabrizio Giudici commented on MGPG-17:
--------------------------------------

My problem is similar, in a batch environment, but it's intermittent. Sometimes it takes the password specified by the property, other times it fails about not being able to use /dev/tty (which is obvious, since it's a batch run, but the bug is that it doesn't use the password specified in the property). I'm seeing the "obsolete option" warning too.

> password is specified, but still promting
> -----------------------------------------
>
>                 Key: MGPG-17
>                 URL: http://jira.codehaus.org/browse/MGPG-17
>             Project: Maven 2.x GPG Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-4
>         Environment: Apache Maven 2.2.0 (r788681; 2009-06-26 08:04:01-0500)
> Java version: 1.6.0_15
> Java home: /usr/lib/jvm/java-1.6.0-sun-1.6.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.27.29-0.1-default" arch: "i386" Family: "unix"
> gpg (GnuPG) 2.0.9
> on OpenSUSE 11.1
>            Reporter: Albert Kurucz
>
> Using
> mvn verify -Dgpg.passphrase=thephrase
> with thephrase replaced with the real one.
> When it get to signing, it still promts.
> It is critical, because this prompt repeats with all the 100 modules of the project.
> Problem maybe related to updates/changes of gpg software.
> Related warning message:
> gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
> can't connect to `/home/albert_kurucz/.gnupg/S.gpg-agent': No such file or directory

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