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>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.1</version>
<configuration>
<mavenExecutorId>forked-path</mavenExecutorId>
<arguments>-Prelease</arguments>
<remoteTagging>false</remoteTagging>
</configuration>
</plugin>
</plugins>
</pluginManagement>
....
<profile>
<id>release</id>
<build>
<plugins>
....
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>1.1</version>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals>
<goal>sign</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 <[email protected]> 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: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
