-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle plugin 1.1 fails to run task #250
Comments
This should be fixed in head, we just need someone to release the fixed version. |
Thanks! |
@KengoTODA, @jsotuyod : who did the last gradle plugin release? Is there some "how to" available? |
@iloveeclipse it's been some time since I last released, I don't know if @KengoTODA did it in the meantime. Unfortunately the Gradle plugin portal is quite new, and has no real support for teams. We have to share the same API key to release, and it has to remain private so it has to be shared and stored outside of git. I'll gladly share it along a small how-to on how to release the plugin with any member willing to do it. In the meantime I'm willing to make a new release if it's ready. Are there any pending issues affecting the plugin to refrain from performing a 1.2 release? |
You could have Travis release when a tag is created and store the keys their as a hidden environmental variable. This was a nifty trick that a contributor to my gradle-versions-plugin added: deploy:
provider: script
script: ./gradlew bintrayUpload
skip_cleanup: true
on:
branch: master
tags: true |
I think we are ready for RC4. |
I would like to try out SpotBugs in a my Gradle Project JabRef and a missing release is kind of a blocker for me. Is it possible to release an update of the plugin. I think, a release of a new version of SpotBugs ist not required, is it? Plugin version 1.0 also does not work, because of #1. When checking https://github.com/spotbugs/spotbugs/milestone/1, I think, a full release of 3.10 is not too far away. 🎉 |
The 1.0 release runs fine, but when updated the task fails.
The text was updated successfully, but these errors were encountered: