Open voor opened 7 years ago
So I'm able to successful have the signing work when I follow the documentation at "Configure GPG passphrase under settings.xml" on http://www.mojohaus.org/rpm-maven-plugin/usage.html (by the way there should be a link to that from http://www.mojohaus.org/rpm-maven-plugin/adv-params.html#Signatures to cut down on confusion) however, I'm still unsure of how to completely disable signing and do that on a later step.
Actually, even with the usage properly setting a gpg server id, I'm still having failures.
If I pass in a different global settings.xml
file that has never populated the gpg
variables I am able to build successfully, but I want an explicit option to essentially say "I realize those variables are populated, but please do not sign the RPM"
I had the same issue, needed to skip the GPG signing since it was going to be taken care of later anyways.
I was able to employ a workaround. The relevant part of the configuration is shown below.
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>rpm-maven-plugin</artifactId>
<version>2.2.0</version>
<executions>
<execution>
<id>build-rpm-package</id>
<goals>
<goal>attached-rpm</goal>
</goals>
</execution>
</executions>
<configuration>
<keyPassphrase/> <!-- null disables gpg signing -->
<passphraseServerId/> <!-- null disables gpg signing -->
<keyname/> <!-- null disables gpg signing -->
</configuration>
<plugin>
Sample POM file of issue is here: https://github.com/voor/rpm-signing-example
Inside my m2 settings file I have something like this:
This results in the following stack-trace: