-
Notifications
You must be signed in to change notification settings - Fork 9
/
Copy pathMAVEN_RELEASE_STEPS
46 lines (31 loc) · 1.34 KB
/
MAVEN_RELEASE_STEPS
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
38
39
40
41
42
43
44
45
EVE release management (tips & tricks & procedures)
-To get rid of lifecycle-mapping warnings in maven:
#create and get into a temp folder
#mvn archetype:generate -DgroupId=org.eclipse.m2e -DartifactId=lifecycle-mapping -Dversion=1.0.0 -DarchetypeArtifactId=maven-archetype-mojo
#cd lifecycle-mapping
#mvn install
Description of release process:
Requirements:
-Sonatype JIRA account (connected to com.almende, through a separate ticket, ask me:)
-A GPG-key that has been published. ($ gpg --keyserver hkp://pool.sks-keyservers.net --send-keys <KEYNUM>)
1: have a <ver>-SNAPSHOT working copy ready, in parent folder
2: mvn versions:set -DnewVersion=<ver>
3: git commit -a
4: git push --all
5: git branch -b <ver>_release //(version with X at end, e.g. v1.1.X_release)
6: git push --set-upstream origin <ver>_release
7: git checkout master
8: git tag <ver> //(version with prefix 'v', e.g. v1.1.0)
9: git push --tags
10: mvn clean deploy -Prelease
11: Login to: https://oss.sonatype.org (Really login, not just opening the page! )
12: Goto: "Staging repositories" (if you can't find it, you didn't login:) )
13: select comalmende repos
14: click on "close"
<Fix any errors that might popup>
<download and test>
15: click on "release"
16: mvn versions:set -DnewVersion=<ver+1>-SNAPSHOT
17: git commit -a
18: git push --all
19: Tell the world!