No, it's nothing with the gpg-plugin.
What you are doing is something like mvn release:perform
-Dpassphrase=xxxx, right?
Well, the release:perform does a svn checkout to work folder and then
forks a new mvn deploy process. But: It seems like the command-line
properties are not passed over! That's the problem.
Solution:
Define a property in your settings.xml:
<profile>
<id>gpg-passphrase</id>
<properties>
<passphrase>???</passphrase>
</properties>
</profile>
and
either activate it by default:
<activeProfiles>
<activeProfile>gpg-passphrase</activeProfile>
</activeProfiles>
or activate it by adding a -Pgpg-passphrase to the command line.
HTH,
Manfred
On 2/13/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
I think it is the plugin.
check out and changing the code
(GpgSignAttachedMojo)
/**
* The passphrase to use when signing.
*
* @parameter expression="${passphrase}" default-value="xxxxxx"
* @required
*/
private String passphrase;
takes me to another exception, but that can be triggered by my running VPN
-M
On 2/13/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> Looks like the -Dpassphrase get's ignored
>
> [INFO] Executing: mvn deploy --no-plugin-updates -P release,staging
> -DperformRelease=true
>
>
>
> <snip>
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven Apache Plugin Parent
> [INFO] Maven Faces Plugin
> [INFO] Maven Javacc Plugin
> [INFO] Maven i18n Plugin
> [INFO] Maven JDev Plugin
> [INFO] Maven Javascript Plugin
> [INFO] Maven XRTS Plugin
> [INFO] Maven Tag Documentation Report
> [INFO] Apache MyFaces Trinidad Archetype
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO]
----------------------------------------------------------------------------
> [INFO] Building Maven Apache Plugin Parent
> [INFO] task-segment: [release:perform] (aggregator-style)
> [INFO]
----------------------------------------------------------------------------
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: svn --non-interactive checkout
> https://svn.apache.org/repos/asf/incubator/adffaces/tags/maven-plugin-p
> arent-1.0.0-incubating checkout
> [INFO] Working directory: D:\Apache\_release\last\target
> [INFO] Unknown file status: ' '.
> [INFO] Executing: mvn deploy --no-plugin-updates -P release,staging
> -DperformRelease=true
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven Apache Plugin Parent
> [INFO] Maven Faces Plugin
> [INFO] Maven Javacc Plugin
> [INFO] Maven i18n Plugin
> [INFO] Maven JDev Plugin
> [INFO] Maven Javascript Plugin
> [INFO] Maven XRTS Plugin
> [INFO] Maven Tag Documentation Report
> [INFO] Apache MyFaces Trinidad Archetype
>
> On 2/13/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > we use this,
> >
> > <parent>
> > <groupId>org.apache</groupId>
> > <artifactId>apache</artifactId>
> > <version>3</version>
> > </parent>
> >
> > was suggested on the general incubator list
> >
> > On 2/13/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > > On 2/13/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > > > > Please create a new staging folder for tomahawk
> > > > > e.g.
> > > > > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
> > > >
> > > > To get this to work you'll probably have to add
> > > > <distributionManagement><repository> to the trinidad pom.
> > > >
> > > > (I don't think you can override that on the command line.)
> > >
> > > Actually... unless the trinidad pom has myfaces-master as its parent,
> > > this does not apply.
> > >
> > > --
> > > Wendy
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > http://tinyurl.com/fmywh
> >
> > further stuff:
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
