ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-20 05:28:21 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merged in mike-add-gradle-versions (pull request #207)

Browse Source 
Add a version number to gradle and allow "gradle install" to install the core module to the local Maven repository.
This commit is contained in:
Mike Hearn 2016-07-08 10:04:01 +01:00
commit a1177f05c1
4 changed files with 13 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
build.gradle
View File

@ -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()

5
core/build.gradle
View File

@ -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 {

8
docs/source/release-process.rst
View File

@ -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.

3
node/build.gradle
View File

@ -1,6 +1,3 @@
group 'com.r3cev.prototyping'
version '1.0-SNAPSHOT'
apply plugin: 'java'
apply plugin: 'kotlin'
apply plugin: QuasarPlugin