[GRADLE-2138] Repository declared as FileSystemResolver is not considered 'local' Created: 04/Mar/12  Updated: 04/Jan/13  Resolved: 14/Mar/12

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.0-rc-1

Type: Bug
Reporter: Daz DeBoer Assignee: Luke Daley
Resolution: Fixed Votes: 0


There is a difference in behaviour between FileSystemResolver and ivy {} repositories is due to a minor bug in Gradle: we currently have the concept of a "local" repository, that means we use the artifacts directly from the repository without caching. We currently consider repositories declared as "ivy

{ url 'file://....' }

as "local", but we do not consider FileSystemResolver repositories as "local". So FileSystemResolver is impacted by caching, while local ivy {} repositories are not.

Comment by Björn Kautler [ 20/Apr/12 ]

This "fix" voids the workaround for GRADLE-1964.
Is there a new workaround EXCEPT using an HTTP repository which is no real alternative?

Comment by Björn Kautler [ 21/Apr/12 ]

I found a new workaround mentioned at http://issues.gradle.org/browse/GRADLE-1964?focusedCommentId=15375&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15375

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