[GRADLE-1210] apply from: Does not follow redirects Created: 06/Nov/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Bug
Reporter: Lars Heuer Assignee: Unassigned
Resolution: Won't Fix Votes: 5


apply from: 'http://github.com/breskeby/gradleplugins/raw/master/emmaPlugin/emma.gradle'

Github sends a 301 (moved permanently) answer with 'https://github.com/breskeby/gradleplugins/raw/master/emmaPlugin/emma.gradle' and a text/html response body.

Gradle does not follow the redirect but claims that '<html>' is a syntax error.

Comment by Francois Rey [ 16/Nov/10 ]

Workaround: use https instead of http.
Resolution: handle 301 properly
Reference: http://support.github.com/discussions/site/2171-nginx-incorrectly-reports-404s-as-301#comment_3722987

Comment by Kelly Robinson [ 21/Mar/12 ]

Thanks for the workaround Francois, I was running into this same issue trying to use the gradle template plugin and using https worked for me too.

Comment by Eric Berry [ 24/Apr/12 ]

This affects the gradle-templates and gradle-release plugins as well since Launchpad.net redirects on artifact files.

Comment by Davide Cavestro [ 29/May/12 ]

I guess this also happens for the release plugin.

UPDATE: sorry, I previously missed other guys comments

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:49:48 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.