forked from RestComm/sipunit
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathrelease-notes
More file actions
37 lines (27 loc) · 1.16 KB
/
release-notes
File metadata and controls
37 lines (27 loc) · 1.16 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Make sure you have gpg keys
1. gpg --list-keys
2. gpg --list-secret-keys
Test that you can sign a file
1. gpg -ab testfile
Make sure that ~/.m2/settings.xml contains the following profile:
<profile>
<id>release-sign-artifacts</id>
<activation>
<property>
<name>performRelease</name>
<value>true</value>
</property>
</activation>
<properties>
<gpg.passphrase>PASSPHRASE</gpg.passphrase>
<gpg.useagent>true</gpg.useagent>
<gpg.defaultKeyring>false</gpg.defaultKeyring>
</properties>
</profile>
</profiles>
New version of gpg will fail to sign artifacts, to workaround this check https://issues.apache.org/jira/browse/MGPG-59
and run:
gpg --use-agent --armor --detach-sign --output $(mktemp) pom.xml
This command will bring up the window to put your passphrase and will create a temp file to be used during the release process.
mvn release:prepare -Pmaven-release --batch-mode -DdevelopmentVersion=2.0.4-SNAPSHOT -DreleaseVersion=2.0.3 -Dtag=2.0.3 -Darguments="-Dmaven.test.skip=true"
mvn release:perform -Pmaven-release,release-sign-artifacts -Darguments="-Dmaven.test.skip=true"