[GRADLE-2934] Use case for custom ivy resolvers (marked as deprecated for 2.x) Created: 24/Oct/13 Updated: 10/Feb/17 Resolved: 10/Feb/17
there is a demand for custom ivy resolvers, so in my opinion they should be supported in 2.x:
We are using an ivy repository via Perforce (https://github.com/sbrabec/ivyp4) which has many benefits over the "traditional" separation of source and binary repositories:
1. No additional infrastructure (maven,artifactory,archiva) needed, which saves costs for IT (same backup & restore, same server, same licensing).
So we would appreciate if the custom ivy resolver will be still available in gradle >= 2.x. If it is of any help I could supply a demo project/perforce server showing the setup.
|Comment by Adam Murdoch [ 10/Nov/13 ]|
We're not going to support Ivy resolvers in Gradle 2.0. However, we do want to support the use cases they are currently used for. It looks to me you can use the existing Gradle repository DSL for all of the use cases above, using either a file URL for local stuff in perforce, or an http URL pointing at your team city instance.
|Comment by Francois Valdy [ 16/Dec/14 ]|
One thing that can no longer be supported is http-based repositories w/o support for HEAD http request.
Examples of web servers that don't support HEAD request (test with https://www.hurl.it):
Hacking support for those in 2.X goes beyond acceptable:
Second thing that is no longer (easily) accessible is the support for custom artifact lister (was used in this plugin as well).
Maybe I'm the only one still relying on such crappy things, so I'll have to find another approach to migrate on 2.X
|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.