[
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
