From ad3e9be1c80d9d6f2b675cac6e7d98ea64fea8c9 Mon Sep 17 00:00:00 2001
From: Mike Hearn <mike@r3cev.com>
Date: Wed, 6 Jul 2016 17:54:46 +0100
Subject: [PATCH] Add a version number to gradle and allow "gradle install" to
 install the core module to the local Maven repository.

---
 build.gradle                    | 8 ++++++--
 core/build.gradle               | 5 ++---
 docs/source/release-process.rst | 8 +++++---
 node/build.gradle               | 3 ---
 4 files changed, 13 insertions(+), 11 deletions(-)

diff --git a/build.gradle b/build.gradle
index 39d87a3993..2d258f4d8a 100644
--- a/build.gradle
+++ b/build.gradle
@@ -1,5 +1,4 @@
-group 'com.r3cev.prototyping'
-version '1.0-SNAPSHOT'
+group 'com.r3corda'
 
 apply plugin: 'java'
 apply plugin: 'kotlin'
@@ -41,6 +40,11 @@ buildscript {
     }
 }
 
+allprojects {
+    // Our version: bump this on release.
+    group 'com.r3corda'
+    version '0.2-SNAPSHOT'
+}
 
 repositories {
     mavenLocal()
diff --git a/core/build.gradle b/core/build.gradle
index 1de8918861..33e81bafc6 100644
--- a/core/build.gradle
+++ b/core/build.gradle
@@ -1,9 +1,8 @@
-group 'com.r3cev.prototyping'
-version '1.0-SNAPSHOT'
-
 apply plugin: 'java'
 apply plugin: 'kotlin'
 apply plugin: QuasarPlugin
+// Applying the maven plugin means this will get installed locally when running "gradle install"
+apply plugin: 'maven'
 
 buildscript {
     repositories {
diff --git a/docs/source/release-process.rst b/docs/source/release-process.rst
index 7116ba0b09..5cdf4201c9 100644
--- a/docs/source/release-process.rst
+++ b/docs/source/release-process.rst
@@ -33,10 +33,12 @@ Steps to cut a release
    create one, bug them to do so a day or two before the release.
 4. Regenerate the docsite if necessary and commit.
 5. Create a branch with a name like `release-M0` where 0 is replaced by the number of the milestone.
-6. Tag that branch with a tag like `release-M0.0`
-7. Push the branch and the tag to git.
-8. Write up a short announcement containing the summary of new features, changes, and API breaks. Send it to the
+6. Adjust the version in the root build.gradle file to take out the -SNAPSHOT and commit it on the branch.
+7. Tag the branch with a tag like `release-M0.0`
+8. Push the branch and the tag to git.
+9. Write up a short announcement containing the summary of new features, changes, and API breaks. Send it to the
    r3dlg-awg mailing list.
+10. On master, adjust the version number in the root build.gradle file upwards.
 
 If there are serious bugs found in the release, backport the fix to the branch and then tag it with e.g. `release-M0.1`
 Minor changes to the branch don't have to be announced unless it'd be critical to get all developers updated.
\ No newline at end of file
diff --git a/node/build.gradle b/node/build.gradle
index f2bf98796b..8a289161b5 100644
--- a/node/build.gradle
+++ b/node/build.gradle
@@ -1,6 +1,3 @@
-group 'com.r3cev.prototyping'
-version '1.0-SNAPSHOT'
-
 apply plugin: 'java'
 apply plugin: 'kotlin'
 apply plugin: QuasarPlugin