Repository navigation
Expand file tree
/
Copy pathRELEASING.txt
More file actions
76 lines (54 loc) · 1.88 KB
/
Copy pathRELEASING.txt
File metadata and controls
76 lines (54 loc) · 1.88 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
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
# Releasing JavaTuples
## 1. Configuration
Configure access to the snapshots and staging servers in `settings.xml`:
```xml
<servers>
<server>
<id>central</id>
<username>[TOKEN USERNAME FROM CENTRAL]</username>
<password>[TOKEN PASSWORD FROM CENTRAL]</password>
</server>
<server>
<id>central-portal-snapshots</id>
<username>[TOKEN USERNAME FROM CENTRAL]</username>
<password>[TOKEN PASSWORD FROM CENTRAL]</password>
</server>
</servers>
```
## 2. Check dependency snapshots
If this is an GA or RC version of JavaTuples being published, check that no
dependencies are in SNAPSHOT version.
If any SNAPSHOTs exist, set to a fixed version and commit.
## 3. Set the new version
```shell
mvn versions:set -DprocessAllModules=true -DnewVersion=X.Y.Z
mvn versions:commit
git add .
git commit -m "Prepare release javatuples-X.Y.Z"
git push
```
## 4. Create and deploy the release into the staging repositories
```shell
mvn -P releases clean compile deploy
```
## 5. Create tag and set to new development version
```shell
mvn scm:tag -Dtag=javatuples-X.Y.Z
mvn versions:set -DprocessAllModules=true -DnewVersion=X.Y.[Z+1]-SNAPSHOT
mvn versions:commit
git add .;
git commit -m "Prepare for next development iteration"
git push
```
## 6. Reset dependency snapshots
If any SNAPSHOT dependencies had to have their versions fixed before building, go
back to SNAPSHOT versions wherever needed and commit.
## 7. Manage deployment in Central
Follow instructions at https://central.sonatype.org/publish/publish-guide/
## 8. Releasing distribution artifacts
Once jar artifacts have been published in Maven Central, the .zip distribution release
generated in dist/target should be uploaded to the GitHub repository as a new release
along with a gpg signature (.asc) generated with:
```shell
gpg -ab --default-key key_ID_for_releases@arxila.io javatuples-X.Y.Z-dist.zip
```