Re: Maven gpg plugin stuck while signing
It worked adding the
configuration
mavenExecutorIdforked-path/mavenExecutorId
/configuration
to the maven-release-plugin, many thanks again Simo! :-)
Cheers,
Tommaso
2011/1/24 Tommaso Teofili tommaso.teof...@gmail.com
Many thanks Simo! :-)
I'm going to try this way and let you know.
Cheers,
Tommaso
2011/1/23 Simone Tripodi simonetrip...@apache.org
Hi Oliver,
sure you can do it, just move the gpg plugin into a proper 'release'
profile, and configure the release-plugin to activate it when
releasing.
Take a look how I configured the Google Doclava[1] pom to see how it
works, follow below some snippets.
HTH, all the best,
Simo
{code}
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
mavenExecutorIdforked-path/mavenExecutorId
arguments-Prelease/arguments
remoteTaggingfalse/remoteTagging
/configuration
/plugin
/plugins
/pluginManagement
profile
idrelease/id
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-gpg-plugin/artifactId
version1.1/version
executions
execution
idsign-artifacts/id
phaseverify/phase
goals
goalsign/goal
/goals
/execution
/executions
/plugin
{code}
[1]
http://code.google.com/p/doclava/source/browse/tags/doclava-1.0.2/pom.xml
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Jan 23, 2011 at 7:37 PM, oliver oliver.bo...@gmail.com wrote:
Am 23.01.2011 um 18:51 schrieb Simone Tripodi:
Ciao Tommy ;)
I already met this problem, It's not a of key-size related issue. Try
setting the mavenExecutorId=forked-path so when releasing maven will
be forked and the gpg-plugin will prompt you insert the gpg
passphrase.
Otherwise you can use the -Dgpg.passphrase=XXX property but its use is
discouraged and you can easily understand why.
yes, that's clear. Is it possible to disable the gpg-plugin for the
daily build?
regards,
Oliver
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven gpg plugin stuck while signing
Hi all, I'm using the Maven release plugin (in dryRun mode) to prepare a release but the mvn release:prepare -DdryRun=true command gets stuck while signing the artifacts with gpg-plugin. Here's what I see in normal mode: ... [INFO] [INFO] Building zip: /Users/tommasoteofili/Documents/workspaces/uima/sandbox/BSFAnnotator/target/uimaj-an-bsf-bin.zip [INFO] [INFO] [INFO] [INFO] --- maven-gpg-plugin:1.1:sign (default) @ BSFAnnotator --- ... and this is the output with debug enabled (-X): ... [INFO] [DEBUG] Configuring mojo org.apache.maven.plugins:maven-gpg-plugin:1.1:sign from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-gpg-plugin:1.1, parent: ClassRealm[maven.api, parent: null]] [INFO] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-gpg-plugin:1.1:sign' with basic configurator -- [INFO] [DEBUG] (f) ascDirectory = /Users/tommasoteofili/Documents/workspaces/uima/sandbox/BSFAnnotator/target/gpg [INFO] [DEBUG] (f) interactive = true [INFO] [DEBUG] (f) project = MavenProject: org.apache.uima:BSFAnnotator:2.3.1-SNAPSHOT @ /Users/tommasoteofili/Documents/workspaces/uima/sandbox/BSFAnnotator/pom.xml [INFO] [DEBUG] (f) skip = false [INFO] [DEBUG] (f) useAgent = false [INFO] [DEBUG] -- end configuration -- [INFO] [DEBUG] Extension realms for project org.apache.uima:parent-pom:pom:2: (none) [INFO] [DEBUG] Looking up lifecyle mappings for packaging pom from ClassRealm[plexus.core, parent: null] ... My GPG key is 4096 bit, is that too much? Side note: I am using Maven 3.0 with Java 6 on a Mac 10.6. Thanks in advance for any help. Tommaso
Re: Maven gpg plugin stuck while signing
Ciao Tommy ;)
I already met this problem, It's not a of key-size related issue. Try
setting the mavenExecutorId=forked-path so when releasing maven will
be forked and the gpg-plugin will prompt you insert the gpg
passphrase.
Otherwise you can use the -Dgpg.passphrase=XXX property but its use is
discouraged and you can easily understand why.
HTH
Simo
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.X/version
configuration
mavenExecutorIdforked-path/mavenExecutorId
/configuration
/plugin
{code}
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Jan 23, 2011 at 12:13 PM, Tommaso Teofili
tommaso.teof...@gmail.com wrote:
Hi all,
I'm using the Maven release plugin (in dryRun mode) to prepare a release but
the
mvn release:prepare -DdryRun=true
command gets stuck while signing the artifacts with gpg-plugin.
Here's what I see in normal mode:
...
[INFO] [INFO] Building zip:
/Users/tommasoteofili/Documents/workspaces/uima/sandbox/BSFAnnotator/target/uimaj-an-bsf-bin.zip
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.1:sign (default) @ BSFAnnotator ---
...
and this is the output with debug enabled (-X):
...
[INFO] [DEBUG] Configuring mojo
org.apache.maven.plugins:maven-gpg-plugin:1.1:sign from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-gpg-plugin:1.1, parent:
ClassRealm[maven.api, parent: null]]
[INFO] [DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-gpg-plugin:1.1:sign' with basic configurator
--
[INFO] [DEBUG] (f) ascDirectory =
/Users/tommasoteofili/Documents/workspaces/uima/sandbox/BSFAnnotator/target/gpg
[INFO] [DEBUG] (f) interactive = true
[INFO] [DEBUG] (f) project = MavenProject:
org.apache.uima:BSFAnnotator:2.3.1-SNAPSHOT @
/Users/tommasoteofili/Documents/workspaces/uima/sandbox/BSFAnnotator/pom.xml
[INFO] [DEBUG] (f) skip = false
[INFO] [DEBUG] (f) useAgent = false
[INFO] [DEBUG] -- end configuration --
[INFO] [DEBUG] Extension realms for project
org.apache.uima:parent-pom:pom:2: (none)
[INFO] [DEBUG] Looking up lifecyle mappings for packaging pom from
ClassRealm[plexus.core, parent: null]
...
My GPG key is 4096 bit, is that too much?
Side note: I am using Maven 3.0 with Java 6 on a Mac 10.6.
Thanks in advance for any help.
Tommaso
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven gpg plugin stuck while signing
Am 23.01.2011 um 18:51 schrieb Simone Tripodi: Ciao Tommy ;) I already met this problem, It's not a of key-size related issue. Try setting the mavenExecutorId=forked-path so when releasing maven will be forked and the gpg-plugin will prompt you insert the gpg passphrase. Otherwise you can use the -Dgpg.passphrase=XXX property but its use is discouraged and you can easily understand why. yes, that's clear. Is it possible to disable the gpg-plugin for the daily build? regards, Oliver - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven gpg plugin stuck while signing
Hi Oliver,
sure you can do it, just move the gpg plugin into a proper 'release'
profile, and configure the release-plugin to activate it when
releasing.
Take a look how I configured the Google Doclava[1] pom to see how it
works, follow below some snippets.
HTH, all the best,
Simo
{code}
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
mavenExecutorIdforked-path/mavenExecutorId
arguments-Prelease/arguments
remoteTaggingfalse/remoteTagging
/configuration
/plugin
/plugins
/pluginManagement
profile
idrelease/id
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-gpg-plugin/artifactId
version1.1/version
executions
execution
idsign-artifacts/id
phaseverify/phase
goals
goalsign/goal
/goals
/execution
/executions
/plugin
{code}
[1] http://code.google.com/p/doclava/source/browse/tags/doclava-1.0.2/pom.xml
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Jan 23, 2011 at 7:37 PM, oliver oliver.bo...@gmail.com wrote:
Am 23.01.2011 um 18:51 schrieb Simone Tripodi:
Ciao Tommy ;)
I already met this problem, It's not a of key-size related issue. Try
setting the mavenExecutorId=forked-path so when releasing maven will
be forked and the gpg-plugin will prompt you insert the gpg
passphrase.
Otherwise you can use the -Dgpg.passphrase=XXX property but its use is
discouraged and you can easily understand why.
yes, that's clear. Is it possible to disable the gpg-plugin for the daily
build?
regards,
Oliver
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven gpg plugin stuck while signing
Many thanks Simo! :-)
I'm going to try this way and let you know.
Cheers,
Tommaso
2011/1/23 Simone Tripodi simonetrip...@apache.org
Hi Oliver,
sure you can do it, just move the gpg plugin into a proper 'release'
profile, and configure the release-plugin to activate it when
releasing.
Take a look how I configured the Google Doclava[1] pom to see how it
works, follow below some snippets.
HTH, all the best,
Simo
{code}
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
mavenExecutorIdforked-path/mavenExecutorId
arguments-Prelease/arguments
remoteTaggingfalse/remoteTagging
/configuration
/plugin
/plugins
/pluginManagement
profile
idrelease/id
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-gpg-plugin/artifactId
version1.1/version
executions
execution
idsign-artifacts/id
phaseverify/phase
goals
goalsign/goal
/goals
/execution
/executions
/plugin
{code}
[1]
http://code.google.com/p/doclava/source/browse/tags/doclava-1.0.2/pom.xml
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Jan 23, 2011 at 7:37 PM, oliver oliver.bo...@gmail.com wrote:
Am 23.01.2011 um 18:51 schrieb Simone Tripodi:
Ciao Tommy ;)
I already met this problem, It's not a of key-size related issue. Try
setting the mavenExecutorId=forked-path so when releasing maven will
be forked and the gpg-plugin will prompt you insert the gpg
passphrase.
Otherwise you can use the -Dgpg.passphrase=XXX property but its use is
discouraged and you can easily understand why.
yes, that's clear. Is it possible to disable the gpg-plugin for the daily
build?
regards,
Oliver
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
