forked from caspark/eclipse-multicursor
-
Notifications
You must be signed in to change notification settings - Fork 0
/
RELEASING
69 lines (50 loc) · 2.98 KB
/
RELEASING
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
Release Process
===============
You do not need to follow these steps if you only want to build a version for personal use (see the README).
Please do not release this project if you are not the current maintainer.
Scripted
--------
Use the release script and specify: the release version, the next development version, and the directory to copy the built artifacts to. For example, to release v0.1.1 and have the next version being developed be 0.1.2(-SNAPSHOT):
mkdir -p ~/tmp/release && ./release.sh 0.1.1 0.1.2 ~/tmp/release && ls ~/tmp/release
Manually
--------
# Update the version in the pom files to the release version (e.g. 0.1.0):
com.asparck.eclipse.multicursor.feature/pom.xml
com.asparck.eclipse.multicursor.p2updatesite/pom.xml
com.asparck.eclipse.multicursor.plugin/pom.xml
com.asparck.eclipse.multicursor.target/pom.xml
com.asparck.eclipse.multicursor.tests/pom.xml
pom.xml
# Update the OSGi manifest versions to the release version (e.g. 0.1.0):
com.asparck.eclipse.multicursor.plugin/META-INF/MANIFEST.MF
com.asparck.eclipse.multicursor.tests/META-INF/MANIFEST.MF
# Update the feature version and the plugin version in the P2 feature definition to the release version (e.g. 0.1.0):
com.asparck.eclipse.multicursor.feature/feature.xml
# Update the feature version and filename in the P2 update site category definition to the release version and release filename (e.g. 0.1.0 and features/com.asparck.eclipse.multicursor.feature_0.1.0.jar)
com.asparck.eclipse.multicursor.p2updatesite/category.xml
# Build the release:
mvn clean verify
# Commit and tag the release:
git commit -a -m "Release: prepare for v$RELEASE_VERSION release"
git tag v$RELEASE_VERSION
# Update the version in the pom files to the new Maven development version (e.g. 0.1.1-SNAPSHOT):
com.asparck.eclipse.multicursor.feature/pom.xml
com.asparck.eclipse.multicursor.p2updatesite/pom.xml
com.asparck.eclipse.multicursor.plugin/pom.xml
com.asparck.eclipse.multicursor.target/pom.xml
com.asparck.eclipse.multicursor.tests/pom.xml
pom.xml
# Update the OSGi manifest versions to the new OSGi development version (e.g. 0.1.1.qualifier):
com.asparck.eclipse.multicursor.plugin/META-INF/MANIFEST.MF
com.asparck.eclipse.multicursor.tests/META-INF/MANIFEST.MF
# Update the feature version and the plugin version in the P2 feature definition to the new OSGi development version (e.g. 0.1.1.qualifier):
com.asparck.eclipse.multicursor.feature/feature.xml
# Update the feature version and filename in the P2 update site category definition to the new OSGI development version and development filename (e.g. 0.1.1.qualifier and features/com.asparck.eclipse.multicursor.feature_0.1.1.qualifier.jar)
com.asparck.eclipse.multicursor.p2updatesite/category.xml
# Verify the development version works:
mvn clean verify
# Commit and push changes:
git commit -a -m "Release: prepare for next development cycle"
git push
# Publish a release on github and upload the P2 update site + plugin jar as binaries.
https://github.com/caspark/eclipse-multicursor/releases/new