[GRADLE-2070] Excessive artifact download when using SFTP resolver Created: 27/Jan/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


 Description   

I'm currently using an Ivy repository accessed via SFTP. I haven't been able to figure out how to use the ivy { } block with SFTP, so I'm doing (roughly) the following:

repositories {
def repo = new org.apache.ivy.plugins.resolver.SFTPResolver()
configure(repo) {
....
}
add(repo)
}

When I try to run my build with M7, I see it redownloading all the jars, but I don't see it trying to download .sha1 or .md5 files. All the artifacts are already present in artifacts-4.

Does duplicate artifact detection only work inside an ivy{} block? Is there something else I need to do to get Gradle to reuse what it already has?

 Comments   
Comment by Gradle Forums [ 27/Jan/12 ]

No, re-using cached artifacts based on SHA1 keys does not work when you use an ivy resolver directly. This behaviour is only available for repositories declared as ivy{}, maven{} and mavenRepo().

Soon we will be working on extending the flexibility and use cases supported by these repository declarations. However, SFTP transport is not currently on the roadmap, and is not likely to be implemented before 1.0 (unless we receive a user contribution!).

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