-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathRELEASING.txt
37 lines (26 loc) · 1.27 KB
/
RELEASING.txt
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
36
37
In order to prepare a release, this steps have to be taken:
1. In settings.xml, these entries must exist:
<profiles>
<profile>
<id>releases</id>
<properties>
<gpg.keyname>[KEYNAME (EMAIL)]</gpg.keyname>
<gpg.passphrase>[GPG PASSPHRASE]</gpg.passphrase>
</properties>
</profile>
</profiles>
<servers>
<server>
<id>sonatype-nexus-snapshots</id>
<username>[USER IN SONATYPE NEXUS]</username>
<password>[PASSWORD IN SONATYPE NEXUS]</password>
</server>
</servers>
2. Ensure all SCM URLs in pom.xml are pointing to the correct github repos like "[email protected]:[user]/[repo].git"
3. Ensure the "dev" branch is totally merged into "master" and pushed to github, and checkout into "master".
4. Deploy SNAPSHOT artifact to Sonatype NEXUS with "mvn deploy", and check in Nexus web interface.
5. Execute a run of the release:prepare goal: "mvn -Preleases release:prepare"
6. Upload the release: "mvn -Preleases release:perform"
7. Merge "master" into "dev", and push. Checkout into the new version tag and merge it into the -dev branch for
the current x.x version (or create this branch).
8. Follow instructions for Nexus at: http://nexus.sonatype.org/oss-repository-hosting.html