[GRADLE-2247] Gradle cannot resolve dependencies when using ivy repository in layout 'gradle' Created: 21/Apr/12  Updated: 04/Jan/13  Resolved: 22/Apr/12

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

Type: Bug
Reporter: Jochen Hinrichsen Assignee: Peter Niederwieser
Resolution: Won't Fix Votes: 0


 Description   

I copied the existing .gradle/caches/artifacts-13/ repository into a folder 'offline' and declared an ivy repository

ivy

{ url "offline" layout "gradle" }

Then i removed the .gradle/caches/artifacts-13 directory, and expected gradle to resolve all dependencies via the offline folder. It does not work because the 'gradle' layout is not the latest 'wharf' layout. Using log4j as an example, gradle tries to fetch

offline/log4j/log4j/1.2.16/ivy-1.2.16.xml respectively
offline/log4j/log4j/1.2.16/log4j-1.2.16.jar

but the wharf layout looks like

offline/module-metadata/log4j/log4j/1.2.16/674f4c9c2688515137be3d2e70ce3583.ivy.xml respectively
offline/filestore/log4j/log4j/1.2.16/bundle/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar

 Comments   
Comment by Peter Niederwieser [ 22/Apr/12 ]

This isn't a supported scenario. The cache is considered an opaque, Gradle-managed data structure. You can't access it as an Ivy repository. (Also we don't use Wharf anymore.)

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