Gradle cannot resolve dependencies when using ivy repository in layout 'gradle'

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None

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

Activity

Hide
Permalink
Peter Niederwieser added a comment -

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.)

Show
Peter Niederwieser added a comment - 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.)

People

  • Assignee:
    Peter Niederwieser
    Reporter:
    Jochen Hinrichsen
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: