Push artifacts to maven central

[Tom-Ski]

Could you please push to maven central instead of/as well as the Github repo?

We use this plugin in our project setup, and a lot of users are experiencing intermittent connection problems when trying to resolve your plugin from your github maven repository, causing their whole build to fail.

Thanks for your work on this plugin!

[steffenschaefer]

Sorry for the delay. The notification mail got somehow marked as spam :(

I wasn't aware that the GitHub solution is so unreliable. We use a proxy repository at work to not be dependent on the internet connection or availability of public repositories. But I guess, you don't talk about a corporate project.

A few weeks ago I read about the requirements for uploading to maven central. As far as I remember, there are some things missing in the pom created by the existing build.gradle. So the existing releases can't be simply uploaded. And I'm not really sure if it is clever to upload the existing releases with a different pom file than the one used in the repository at GitHub as this could cause ugly inconsistencies ...
Additionally, I didn't read about signing what is also necessary for an upload to maven central.

In the release notes of Gradle I read that there's support for another public repository named JCenter. Potentially this is a possibility to upload the existing releases. I'll have to check this.

[Tom-Ski]

It seems to be a small amount of users that see this, I've encountered it myself twice, once when Github was being DDoS'd, and another just at a random time. (And I setup hundreds of projects to test, so it really is quite rare, for me at least)

The project is Libgdx, if you are interested, https://github.com/libgdx/libgdx , there are a few issues left open that talk about this problem, and it does pop up on the forum/irc from time to time.

I assume its just a case of timing, when their servers are down/blocking too many connections and if you're unlucky. I just assume that using some 'official' repository would provide more stability.

[tbroyer]

+1

I also always think twice before cloning a Git repo that contains binaries: I'm interested in the sources, not the binaries, when cloning a repo.

Finally, GitHub also discourages serving files right from the repo (even for simple JS or CSS or shell scripts; they suggest using gh-pages instead — but in the case of binaries, that just moves the problem to another branch)

Put simply, Git (and DVCS in general) is not designed for storing binaries; putting binaries in a Git repo is an anti-pattern; and using that just to serve the binaries through HTTP on a central repo is even worse.

BTW, to deploy to Central (through oss.sonatype.org), I use the gradle-nexus-plugin (and passing passwords –particularly my GPG one– to Gradle with -P when deploying, rather than storing them in my .gradle/gradle.properties). I haven't tried JCenter (through Bintray) yet.

[steffenschaefer]

I will add the necessary metadata to the generated pom for the next release.

But I guess I won't have enough time in the next 2-3 weeks. Sorry for that :(
I hope this doesn't cause too much trouble on your side.

[steffenschaefer]

The plugin artifacts are now available at Bintray using the URL 'http://dl.bintray.com/steffenschaefer/maven'.

All versions (including the newly released 0.5) are now available at Bintray. I hope it will be available in JCenter in a few days too. I hope this makes using the plugin a little bit more smooth.

[Tom-Ski]

Great stuff, thanks a bunch.