You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gili (JIRA)" <ji...@codehaus.org> on 2013/01/14 06:52:14 UTC

[jira] (MRELEASE-742) Regression in 2.2.2 related to maven-gpg-plugin

    [ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317257#comment-317257 ] 

Gili commented on MRELEASE-742:
-------------------------------

I can confirm this regression. The problem is caused by the fact that version 2.2.2 overrides settings.xml. Here is the command-line of 2.2.2:

{code}
[INFO] Executing: /bin/sh -c cd /home/builds/.jenkins/workspace/cmake/target/checkout && /home/builds/.jenkins/tools/Maven/Maven_auto-install_/bin/mvn -s /tmp/release-settings5386211605411677960.xml deploy --no-plugin-updates -Psonatype-oss-release -P linux,always-active -f pom.xml
{code}

Notice, -s /tmp/release-settings5386211605411677960.xml. Version 2.0 looks identical except it does not override settings.xml. Peeking inside settings.xml I see it stripped the "gpg.passphrase" property set by by the "always-active" profile.

This issue is very serious (no known workaround short of downgrading). Please investigate it right away.
                
> Regression in 2.2.2 related to maven-gpg-plugin
> -----------------------------------------------
>
>                 Key: MRELEASE-742
>                 URL: https://jira.codehaus.org/browse/MRELEASE-742
>             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 http://maven.apache.org/plugins/maven-gpg-plugin/xref/org/apache/maven/plugin/gpg/AbstractGpgMojo.html) 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 value.
> Downgrading to 2.2.1 fixes the problem and the built artifacts are correctly signed.
> An example POM project can be found at:
> http://code.google.com/p/derquinse-commons/source/browse/trunk/derquinse-pom/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira