Publish to bintray instead of tellurianring.com about gradle-release HOT 20 CLOSED

I'd much rather be publishing to a maven repository too. I'll sign up for the beta and see what happens. Thanks for the pointer.

from gradle-release.

Vote for this change

from gradle-release.

I too am uneasy about relying on the 'tellurianring.com' web-site. How would I go about downloading and including the plugin in the SCM of my target project?

from gradle-release.

You could put plugin into buildSrc folder of project. Like described in Gradle Docs
Here's an example, the dummy project I've used to test gradle-release

from gradle-release.

I've been working on getting this into bintray but I can't seem to publish snapshot versions. If I just want release versions I can use the ivy deployer - the maven deployer throws the same error found here: https://gist.github.com/johnrengelman/4677898, and unfortunately I'm unable to move to Java 7 at this time. It's been a while, but the last time I used Ivy directly there wasn't an easy way to publish snapshot versions to a maven repo using Ivy. Anyone have experience with this and can provide help, it'd be much appreciated.

from gradle-release.

Bintray does not support snapshots right now.

On Tue, Mar 19, 2013 at 12:36 PM, townsfolk [email protected]:

I've been working on getting this into bintray but I can't seem to publish
snapshot versions. If I just want release versions I can use the ivy
deployer - the maven deployer throws the same error found here:
https://gist.github.com/johnrengelman/4677898, and unfortunately I'm
unable to move to Java 7 at this time. It's been a while, but the last time
I used Ivy directly there wasn't an easy way to publish snapshot versions
to a maven repo using Ivy. Anyone have experience with this and can provide
help, it'd be much appreciated.

—
Reply to this email directly or view it on GitHubhttps://github.com/townsfolk/gradle-release/issues/19#issuecomment-15137979
.

from gradle-release.

Ok. Well, I'd prefer to have one solution for snapshots and releases so you'll have to live with the jars being hosted on tellurianring.com - I've had the host for many years and I host the jedit daily builds there without having any issues, so it's quite reliable. I understand the desire for a maven repo though, and I think I've figured out how to make it work on tellurianring.com. The apply scripts will stay the same, but you should be able to get the jars via maven (or repo proxy) as well.

from gradle-release.

Leaving releases of this plugin on tellurianring.com is limiting its adoption. It's a solid plugin and deserves to used more widely. From an outsider point of view, having one place for releases and one place for snapshots isn't a problem at all. It seems perfectly reasonable to publish a release to both tellurianring.com and bintray/maven central.

from gradle-release.

Thank you for your opinion, but I honestly doubt my hosting the jar files is limiting it's adoption. I'm sure it's adoption is much more limited by lack of exposure than anything else. The real issue here is Gradle's own lack of a formal plugin portal (which is in the works from my understanding: http://forums.gradle.org/gradle/topics/plugin_portal_improving_plugin_development). Until there's an official solution all plugin developers are basically left to figure out hosting on their own. There are plenty of very popular plugins out there that don't have "official" maven repository hosting, or provide binaries at all and require people to download the source.

That being said, I have solutions locally for both bintray and tellurianring, so having releases go to bintray and snapshots be available via tellurianring will be easy enough to do.

from gradle-release.

I take that back. Bintray is not working at all.. I can upload the jar files, but if I use the ivy repository to upload it fails on the ivy.xml upload, if I use the maven deployer it fails with the aforementioned error. Sorry guys, I don't have a lot of time for this and I've spent too much on bintray already.. if someone wants to tell me how to deploy from gradle to bintray I'll set this up... for now you'll just have to live with my hosting.

from gradle-release.

If you'd like to use the latest snapshot version, this will work as the apply from url:
http://tellurianring.com/projects/gradle-plugins/gradle-release/1.2-SNAPSHOT/apply.groovy

If you want to proxy the m2 repo, use:
http://tellurianring.com/projects/gradle-plugins/repo

Only the 1.2-SNAPSHOT version is available right now. I plan on doing another release really soon to get out eshepelyuk's changes for jgit.

from gradle-release.

I successfully used mavenDeployer to publish my gradle-site-plugin to Bintray (my build.gradle). I manually created the repository, package, and version prior to attempting the gradle upload. I didn't run into the IllegalArgumentException mentioned in the gist you pointed out.

As @quidryan pointed out, Bintray doesn't support snapshots for now. The Sonatype OSS Maven Repository does, however. If you publish there, it would allow publishing both snapshots and releases, and relatively easily publishing the releases to Maven Central.

from gradle-release.

I tried the Bintray.gradle file a couple of days ago. I can't remember why didn't work for me. In either case, I'd still prefer to have both snapshots and releases in one place. Thank you very much for the pointer to Sonatype OSS. I'll see if I can get that working.

from gradle-release.

For this usage, the Bintray.gradle file isn't relevant; it only adds convenience extensions to repositories for loading dependencies. At some point I hope to extend it to support extensions for publishing as well, but that doesn't exist yet.

from gradle-release.

Thanks. :)

I was able to get my project approved at Sonatype, so I should be able to publish snapshots and releases there. Anyone have any advice or gotcha's I should look out for? I won't be able to get to it until this weekend.

Thanks all for the help and patience.

from gradle-release.

In case you haven't seen it already, this blog post covers the basic of using Gradle to publish to Sonatype OSS.

from gradle-release.

David, thank you so much for the pointer.

I have it set up to deploy to sonatype now and there is a snapshot version available there.

If you would like to try it, you should be able to use:
"com.github.townsfolk:gradle-release:1.2-SNAPSHOT"

The next official release will go through sonatype - will close the ticket then.

from gradle-release.

Hi, Do you have a schedule for when the next release will be performed?
We have a company policy to only use dependencies through our own nexus instance, and it does not mirror snapshots from external repos.

I think this plugin looks promising and would like to use it.

from gradle-release.

I had planned on doing a release this weekend, but issue #25 has me worried now. I'll update this ticket when I decide.

from gradle-release.

Anyone have any advice on actually doing the release to Sonatype? I followed the jedi coder tutorial, and Sonatype complains about the ASC files being missing.

I followed this forum post:
http://forums.gradle.org/gradle/topics/uploadartifacts_skips_asc_files_during_upload_of_multiple_artifacts_in_multi_module_project

Which gets the asc files for the sources and javadoc jar files, but for some reason the .jar.asc file is skipped.

I've added to that forum post, but thought I'd ask here too.

from gradle-release.