blob: 1a8b501a3c284f1068ff24f785ce8ab960307d62 [file] [log] [blame]
David Pursehouseb8fbb8a2016-08-31 09:33:03 +09001= Making a Snapshot Release of JGit
Saša Živkov38fe2fc2016-02-18 14:00:06 +01002
3This step is only necessary if we need to create an unofficial JGit
4snapshot release and publish it to the
5link:https://developers.google.com/storage/[Google Cloud Storage].
6
David Pursehouseb8fbb8a2016-08-31 09:33:03 +09007[[prepare-environment]]
8== Prepare the Maven Environment
9
10First, make sure you have done the necessary
11link:dev-release-deploy-config.html#deploy-configuration-settings-xml[
12configuration in Maven `settings.xml`].
13
14To apply the necessary settings in JGit's `pom.xml`, follow the instructions
15in link:dev-release-deploy-config.html#deploy-configuration-subprojects[
16Configuration for Subprojects in `pom.xml`], or apply the provided diff by
17executing the following command in the JGit workspace:
18
19----
20 git apply /path/to/gerrit/tools/jgit-snapshot-deploy-pom.diff
21----
Saša Živkov38fe2fc2016-02-18 14:00:06 +010022
23[[prepare-release]]
24== Prepare the Release
25
David Pursehouseb8fbb8a2016-08-31 09:33:03 +090026Since JGit has its own release process we do not push any release tags. Instead
27we will use the output of `git describe` as the version of the current JGit
28snapshot.
29
30In the JGit workspace, execute the following command:
Saša Živkov38fe2fc2016-02-18 14:00:06 +010031
32----
33 ./tools/version.sh --release $(git describe)
34----
35
Saša Živkov38fe2fc2016-02-18 14:00:06 +010036[[publish-release]]
37== Publish the Release
38
David Pursehouseb8fbb8a2016-08-31 09:33:03 +090039To deploy the new snapshot, execute the following command in the JGit
40workspace:
Saša Živkov38fe2fc2016-02-18 14:00:06 +010041
Saša Živkov38fe2fc2016-02-18 14:00:06 +010042----
43 mvn deploy
44----
45
46
47GERRIT
48------
49Part of link:index.html[Gerrit Code Review]
50
51SEARCHBOX
52---------