Upload built artifacts to relevant repositories

[ulises]

Would it be possible to upload jar files to maven central?

[irmen]

Probably, but I've got no time to research on how to do that. Can you provide the necessary details?

[ulises]

It's a bit long, but the process is explained here: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

[irmen]

Not going to do that myself. Pull requests for the appropriate changes gladly accepted.

[ulises]

Fair enough. Will see if I can whip up something together.

[irmen]

Closing this as I'm not going to work on this myself. Pull requests still accepted.

[mausch]

It seems that packages are available here: http://mvnrepository.com/artifact/org.spark-project/pyrolite

[irmen]

Hm. That has not been put there by me. Also, it is quite an old version, trailing behind several releases...

[JoshRosen]

The org.spark-project.pyrolite artifact was published by the Apache Spark project, which depends on Pyrolite. We'd like to upgrade to a newer Pyrolite release, which will require a new artifact to be published. We could do this ourselves under our own namespace, but I'd prefer to help Pyrolite publish its own official Maven releases.

The biggest hassles occur up-front, after which publishing new releases is pretty easy. There's an updated guide at http://central.sonatype.org/pages/ossrh-guide.html, which has a subsection on configuring your Ant build file for compatibility with Maven Central's publishing conventions.

I'd be glad to help with whatever build changes are necessary to get this published.

(/cc @davies @mengxr @pwendell, who have some experience with the Maven Central publishing process).

[irmen]

@JoshRosen I will have a look at the guide you linked, thanks for that (but what does Sonatype have to do with maven central? I'm all new to this)

First though, the issues #19, #20 and #25 need fixing :)

[irmen]

@JoshRosen i've tried some things but could use some assistance now, because I seem to be stuck. I started with the https://github.com/irmen/serpent dependency.
I transformed the java part of the project to a maven structure and created a maven pom file based on what instructions I could find. I've created an account at Sonatype.
That's all good but I seem to be stuck at two things: I struggle with maven's handling of version numbers (should or should I not use a -SNAPSHOT postfix? why?) and I have troubles uploading the release to what should be sonatype's staging repository. It doesn't show up. Please see my comment in their JIRA issue https://issues.sonatype.org/browse/OSSRH-15083

[mengxr]

@irmen Public release versions should not have -SNAPSHOT suffix, which is also true for staging. You can also try publishing on bintray first, and then use their service to publish in maven central.

[irmen]

bintray looks a great deal more accessible than sonatype, I'll have a look

[mengxr]

Yes, you can then sync releases to maven central: http://blog.bintray.com/2014/02/11/bintray-as-pain-free-gateway-to-maven-central/. (But I haven't tried it.)