[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

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

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Issue Links:
Duplicates GRADLE-2933 Use case for custom ivy resolvers (ma... Resolved


Hi all,

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 ([1]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).
2. Improving the existing infrastructure (like adding replication servers, failover servers, proxy servers) scales for the binary artifacts "for free". E.g. I use a perforce proxy on my laptop, which also proxies the binaries.
3. Artifacts are versioned using the same atomic number as the sources, which means: I can easily revert, sync to specific dates, examing the commit logs etc. There is only a single source of truth -> Version everything (Perforce marketing The more data sources we have for a build, the harder it is to reproduce e.g. a release build from 5 years ago.
4. Build artifacts are hosted by the CI server (in our case Teamcity, which servers artifacts also via ivy). So there's no need for an additional artifact server.

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.
[1] https://github.com/sbrabec/ivyp4

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.
This used to be hacked around with URLResolver in gradle-repositories-plugin but no longer works with 2.X.

Examples of web servers that don't support HEAD request (test with https://www.hurl.it):
https://www.nuget.org/api/v2/package/ILRepack/1.17 -> 501
http://mb-unit.googlecode.com/files/GallioBundle-3.3.458.0.zip -> 404

Hacking support for those in 2.X goes beyond acceptable:
new DefaultBaseRepositoryFactory(... , customTransportFactory, ...)
+ RepositoryTransportFactory override + HttpTransport override

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:

  • 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 12:35:22 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.