[GRADLE-2083] http status code 403 stops ivy resolver? Created: 06/Feb/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
I am trying to add a build dependency on a url to a jar along the lines of the suggestions in given by Daz DeBoer in the forums here: http://gsfn.us/t/2m4hp
I think I have it working in one case, but another jar on githup doesn't work. What I think is happening is the the Ivy resolver first tries to get the .ivy file, which doesn't exist. But, because the github server returns a "403 Forbidden" instead of a 404, it gives up, even though if it just went ahead and tried to get the jar using the same pattern, it would succeed. To see this, replace ".xml" with ".jar" and the download works.
Is this an ivy or gradle bug? Should I be doing something different so that the lack of the .ivy file does not cause a build failure?
This is with Gradle 1.0-milestone-7.
Here is the build.gradle, using the izpack plugin as a test case:
And the output:
FAILURE: Build failed with an exception.
Here is another example for a different jar, also where the corresponding .ivy file does not exist:
and the output:
Welcome to Gradle 1.0-milestone-7.
To run a build, run gradle <task> ...
To see a list of available tasks, run gradle tasks
To see a list of command-line options, run gradle --help
|Comment by Christian K [ 14/Mar/13 ]|
This should fix it - gradle should not care if there is an exception during fetching the ivy xml.
I worked around the issue by setting ivyPattern to some url that returns a 404
|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:
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.