gradle-release

Install doesn't work.

Asked by Jordan Zimmerman

Added apply from: "http://launchpad.net/gradle-release/trunk/latest/+download/apply.groovy" to my build.gradle. I get:

Task 'release' not found in root project 'foo'.

Question information

Language:
English Edit question
Status:
Answered
For:
gradle-release Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jordan Zimmerman (rz-jordan) said : 		#1

* bump *

Is anyone here?

Revision history for this message
Launchpad Janitor (janitor) said : 		#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Davide Cavestro (d-cavestro) said : 		#3

I guess there is a redirection that gradle does not follow (see http://issues.gradle.org/browse/GRADLE-1210)
I solved the problem using
apply from: "https://launchpadlibrarian.net/89475112/apply.groovy"
instead of
apply from: "http://launchpad.net/gradle-release/trunk/latest/+download/apply.groovy"

Cheers
Davide

Revision history for this message
Davide Cavestro (d-cavestro) said : 		#4

I filed a bug for plugin maintainers at https://bugs.launchpad.net/gradle-release/+bug/1005910
I previously missed comments at http://issues.gradle.org/browse/GRADLE-1210 where was depicted an easier workaround: use the "https" protocol instead of "http"

Cheers
Davide

Revision history for this message
Eric Berry (elberry) said : 		#5

Ugh. Sorry Jordan. For some reason I didn't get a notification when you asked this question on the 6th, or when you bumped it on the 8th.

Thank you Davide for finding a work-a-round. I have updated the documentation to use https vs http. Hopefully that solves it.

However, I also plan on moving over the files to the tellurianring.com server so that they can be statically references instead of the redirect.

Thank you both for reporting the issues.

Revision history for this message
Eric Berry (elberry) said : 		#6

Ugh. Sorry Jordan. For some reason I didn't get a notification when you asked this question on the 6th, or when you bumped it on the 8th.

Thank you Davide for finding a work-a-round. I have updated the documentation to use https vs http. Hopefully that solves it.

However, I also plan on moving over the files to the tellurianring.com server so that they can be statically references instead of the redirect.

Thank you both for reporting the issues.

Can you help with this problem?

Provide an answer of your own, or ask Jordan Zimmerman for more information if necessary.

To post a message you must log in.