Publishing artifacts to Maven Central?

[cartley]

Does anyone know who published the JTK to Maven Central, and how we can go about getting it updated with the current version? The one there is from 14-Dec-2015.

http://search.maven.org/#artifactdetails%7Cedu.mines.jtk%7Cedu-mines-jtk%7C1.0.0%7Cjar

[cartley]

See ad2d061

[chrisengelsma]

I'm guessing @dhale did that? I'm not sure, but I agree we need to go ahead and get that updated.

[dhale]

I did that. I do not remember the details but recall learning the process required for MavenCentral from online docs. My computer while on trail is my iPhone and I type slowly with my thumbs when I get service. I do remember adding something to the gradle build to automate this. I think you need a sonatype account. I will be in Silver City Thursday and Friday. If Chris or Craig want to call me send private email and I will provide my number.

[cartley]

It's not urgent so please enjoy your day off. I gather there is a key used to sign the jar and sonatype login credentials. I think our goal should be to get this rolled into the Mines JTK organization along with a proper ci/cd pipeline. I suspect Chris knows how much of this is possible and how we get started migrating to the github organization, if that is what we want to do.

p.s. ricko observed that you've completed your first degree of latitude. 16.5 more to go!

[chrisengelsma]

We can use the gradle scripts to generate the appropriate pom to upload to Nexus, and from there it can be as simple as uploading the goods using curl.

This does raise another question regarding releases. Right now, the JTK is sort of a continuum - should we start giving thought to segmenting out official releases? Then we can also set the releases here.