Publish the plugin artifact to Maven Central

[netmikey]

I'd also like to be able to get it from maven central into our company's repository server. We cannot download from maven central or any external site directly onto our workstations.

[spina]

I would like to vote for this issue. I may attempt to implement it if I have time...

[aantono]

Will look into this when I get back from vacation :)

[spina]

Any movement on this?

[spina]

Issue 22 had some discussion on how to setup your build script to treat github as a maven repo. I believe that this is a better solution than publishing the jar to Maven Central. I've copied the gradle logic to achieve this here:

buildscript {
    repositories {
        maven { url "https://raw.github.com/valkolovos/gradle_cobertura/master/repo" }
    }
    dependencies {
        classpath "gradle_cobertura:gradle_cobertura:1.2"
    }
}
apply plugin: 'cobertura'

I believe that many external tools (such as artifactory) can be told to search arbitrary maven repos for artifacts. I suspect that with a little configuration, @netmikey could have his company maven server check github for his Jar.

As far as I am concerned, this issue can be closed.

[netmikey]

@spina: why would that be a better solution? Or even: what's wrong with uploading it to maven central, the de facto standard one-stop-get-everything repository in the java world?

The solution you mention would at least work, but our company's repo maintainer would probably kill me if each and every one of our dependencies would require him to add an additional location to mirror. That'd also mean that our repo server would have to check your github repo for every miss on the other repos, which might get quite expensive if you have a lot of em.

All the hosting-at-github stuff is cute and everything, but if you want ppl to use it in corporate environments, maven central is the way you should go, really.

[spina]

@netmikey I wouldn't call it a better solution, but for my use it was sufficient. I agree that this 'belongs' in the Maven Repo, but I didn't feel that I had a right to push for this improvement after I'd found a work around that was more than satisfactory for my needs.

[spina]

As a heads up, there is an extension to this plugin here: https://github.com/stevesaliman/gradle-cobertura-plugin which is in maven central.