Add Gradle logic to allow release publication

[oliverlockwood]

Note that gradle.properties config on the build machine is required to provide the URL, username and password for an actual release.

[chbatey]

Would you mind changing it to use the axion release plugin? that is the one we're standardising on across our libs

[chbatey]

You'll need to put dummy defaults on so it passes on travis and on a fresh checkout e.g https://github.com/scassandra/scassandra-server/blob/master/server/build.gradle

[oliverlockwood]

@chbatey I've updated to use axion, and in fact that's let me release from a branch (which I've done - apologies, I tried running it to check things were generally working, but expected the release operation to fail!) That does at least unblock us to use the new version 0.8.0 in UMV though :smiley:

I'm not entirely clear which part of the scassandra-server build.gradle you're referring to which would ensure this passes on Travis etc. Could you clarify, please?

[chbatey]

if (!project.hasProperty("ossrhUsername")) {
    ext.ossrhUsername = "dummy"
}
if (!project.hasProperty("ossrhPassword")) {
    ext.ossrhPassword = "dummy"
}

it means if ppl don't have the variables defined they can still build but not release

[chbatey]

that example is for a user/pass for maven central

[oliverlockwood]

@chbatey gotcha, cheers, not sure how I missed that.

[jsravn]

resolves #6

[jsravn]

Can you remove the 0.8.0 release that got created on the github project?

edit: I've removed it.

[jsravn]

We shouldn't be tagging the repo until we are releasing this to jcenter proper. Make sure when you run axion to disable the pushing of tags.