maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] (MRELEASE-742) Regression in 2.2.2 related to maven-gpg-plugin
Date Fri, 02 Mar 2012 20:46:02 GMT


Robert Scholte commented on MRELEASE-742:

When running {{release:prepare}} with debugLogging (and dryRun, so you won't actually commit
the changes), can you tell the difference of the configuration of the gpg-plugin?
So {{mvn release:prepare -X -DdryRun=true}}

And from these logs, do you see why these configurations could be different?

> Regression in 2.2.2 related to maven-gpg-plugin
> -----------------------------------------------
>                 Key: MRELEASE-742
>                 URL:
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2.2
>         Environment: OS X 10.6, Maven 3.0.3, maven-gpg-plugin 1.4
>            Reporter: Andres Rodriguez
> After updating to Release Plugin 2.2.2 gpg plugin fails with error:
> "Cannot obtain passphrase in batch mode"
> Which is thrown (see
when the passphrase has not been set and the use agent parameter is
> false. The passphrase is set in my settings.xml and the useAgent has the default false
> Downgrading to 2.2.1 fixes the problem and the built artifacts are correctly signed.
> An example POM project can be found at:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message