You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andres Rodriguez (JIRA)" <ji...@codehaus.org> on 2012/02/25 19:34:02 UTC
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Andres Rodriguez created MRELEASE-742:
-----------------------------------------
Summary: 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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Gili (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317373#comment-317373 ]
Gili commented on MRELEASE-742:
-------------------------------
Hi Robert,
Maven 3.0.3, Ubuntu 12.04, 64-bit.
> 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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Gili (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317257#comment-317257 ]
Gili edited comment on MRELEASE-742 at 1/13/13 11:54 PM:
---------------------------------------------------------
I can confirm this regression. The problem is caused by the fact that version 2.2.2 overrides settings.xml. Here is the output I get from "release:perform" on version 2.2.2:
{code}
[INFO] Invoking perform goals in directory /home/builds/.jenkins/workspace/cmake/target/checkout
[INFO] Executing goals 'deploy'...
[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 and as a result signing works fine. Peeking inside /tmp/release-settings5386211605411677960.xml reveals a file based on ~/.m2/settings.xml except it is missing the "always-active" profile (and as a result the "gpg.passphrase" property is missing).
This issue is very serious (no known workaround short of downgrading). Please investigate it right away.
was (Author: cowwoc):
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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293241#comment-293241 ]
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: 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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317372#comment-317372 ]
Robert Scholte commented on MRELEASE-742:
-----------------------------------------
Gili, what's your environment? Especially which Maven version?
> 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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317375#comment-317375 ]
Robert Scholte commented on MRELEASE-742:
-----------------------------------------
Maven 3.0.4 fixes an issue with {{Profile}} merging in {{settings.xml}} which was there since the first Maven3 release. What you could try: run the project with Maven-3.0.4, and set the [maven-release-plugin#mavenHome|http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#mavenHome] property to Maven-3.0.3
> 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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Gili (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317257#comment-317257 ]
Gili edited comment on MRELEASE-742 at 1/13/13 11:56 PM:
---------------------------------------------------------
I can confirm this regression. The problem is caused by the fact that version 2.2.2 overrides settings.xml. Here is the output I get from "release:perform" on version 2.2.2:
{code}
[INFO] Invoking perform goals in directory /home/builds/.jenkins/workspace/cmake/target/checkout
[INFO] Executing goals 'deploy'...
[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 and as a result signing works fine. Peeking inside /tmp/release-settings5386211605411677960.xml it looks like the plugin took ~/.m2/settings.xml and stripped out the "always-active" profile (which sets the "gpg.passphrase" property).
This issue is very serious (no known workaround short of downgrading). Please investigate it right away.
was (Author: cowwoc):
I can confirm this regression. The problem is caused by the fact that version 2.2.2 overrides settings.xml. Here is the output I get from "release:perform" on version 2.2.2:
{code}
[INFO] Invoking perform goals in directory /home/builds/.jenkins/workspace/cmake/target/checkout
[INFO] Executing goals 'deploy'...
[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 and as a result signing works fine. Peeking inside /tmp/release-settings5386211605411677960.xml reveals a file based on ~/.m2/settings.xml except it is missing the "always-active" profile (and as a result the "gpg.passphrase" property is missing).
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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Gili (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Gili (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317373#comment-317373 ]
Gili edited comment on MRELEASE-742 at 1/15/13 1:36 PM:
--------------------------------------------------------
Hi Robert,
Maven 3.0.3, Ubuntu 12.04, 64-bit. Please note I cannot use Maven 3.0.4 because of this bug: http://jira.codehaus.org/browse/MNG-5363
was (Author: cowwoc):
Hi Robert,
Maven 3.0.3, Ubuntu 12.04, 64-bit.
> 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
[jira] (MRELEASE-742) Regression in 2.2.2 related to
maven-gpg-plugin
Posted by "Gili (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317376#comment-317376 ]
Gili commented on MRELEASE-742:
-------------------------------
Robert,
I'll try what you suggested in a few days (unfortunately I'm tied up with critical work for the next 2 days). On a side-note, can you please give MNG-5363 a nudge? We need someone to update Component, Priority and possibly assign it to the right person. I don't have the necessary permissions.
> 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