Found the issue.
Under the maven-release-plugin there is this configuration section
<configuration>
<!--You need this profile. It'll sign your artifacts.
I'm not sure if this config. actually works though.
I've been specifying -Papache-release on the command-line
-->
<releaseProfiles>apache-release</releaseProfiles>
<!--This stops our running tests for each stage of maven
release.
But it builds the test jar. From SUREFIRE-172.
-->
<arguments>-Dmaven.test.skip.exec</arguments>
<pomFileName>pom.xml</pomFileName>
</configuration>
The arguments line there overrides all the arguments passed in through the
command line.
Once I modified that line to
<arguments>-Dmaven.test.skip.exec -Dgpg.skip=true</arguments>
I was able to skip the gpg signing step.
Thanks,
Enoch Hsu
From: Stack <[email protected]>
To: HBase Dev List <[email protected]>,
Date: 08/25/2014 09:38 PM
Subject: Re: Maven Release to private repository GPG signing
Sent by: [email protected]
On Mon, Aug 25, 2014 at 4:05 PM, Enoch Hsu <[email protected]> wrote:
> I tried splitting it into 2 sets of quotes but that didnt change
anything.
> I did a little more digging and it seems the -Darguments line is being
> overridden by maven somewhere
> In the run logs I am seeing this
> *15:02:01* [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare' with basic
> configurator -->
> *15:02:01* [DEBUG] (f) addSchema = true
> *15:02:01* [DEBUG] (f) allowReleasePluginSnapshot = false
> *15:02:01* [DEBUG] (f) allowTimestampedSnapshots = false
> *15:02:01* [DEBUG] (f) *arguments = -Dmaven.test.skip.exec*
> *15:02:01* [DEBUG] (f) autoVersionSubmodules = false
> *15:02:01* [DEBUG] (s) basedir = /a/workspace/HBase-0.98.4
> *15:02:01* [DEBUG] (f) commitByProject = false
>
> Seems like the arguments is being overridden somewhere and the actual
> command that is being executed is
>
> Executing: /bin/sh -c cd /a/workspace/HBase-0.98.4.release
&& /a/tools/hudson.tasks.Maven_MavenInstallation/maven3/bin/mvn
> -B -X -D maven.repo.local=/a/.m2/repository -s
> /tmp/release-settings839094365501163152.xml -D
> *maven.test.skip.exec=true -P apache-release deploy *
> Any ideas on why the command I'm using is getting overridden by maven?
> Unfortunately signing the artifact during release does not seem to be
> an option that is available for me right now.
>
>
> Thanks,
> Enoch Hsu
>
Try newer maven-release-plugin?
http://mvnrepository.com/artifact/org.apache.maven.release/maven-release-manager/2.5
Maybe it will respect your flagging?
St.Ack
