Ben - Do you mean "~/.ivy2/local" or "~/.ivy2/cache" ?
AFAIK the cache bit is the same in sbt as for Ivy, caveat that we try to ignore what resolver an artifact came from in the store. However, Gradle's cache is a completely different beast, so the I don't think the two are compatible. Now for the local-project, we could very-well have something non-standard in there, although I don't think there *is* a standard. Here's the code/pattern for resolving from the local repo: https://github.com/sbt/sbt/blob/0.13/launch/src/main/scala/xsbt/boot/Update.scala#L379-L387 https://github.com/sbt/sbt/blob/0.13/launch/src/main/scala/xsbt/boot/BootConfiguration.scala#L30-L32 Also, for loading sbt-plugins we add the additional "scala/sbt" universe to the pattern: Someone more qualified than I in the Ivy can answer whether that's a "default" thing. On Thu, Apr 10, 2014 at 3:00 AM, Ben McCann <b...@benmccann.com> wrote: > Hi, > > I'm using SBT and Gradle as build systems. I want them to publish to and > read from ~/.ivy2 but they use and expect default layouts and so they do > not cooperate well each other using this directory. I'm wondering which one > is right and which one is wrong. > > Also, I downloaded the latest ivy source to check what layout it uses. I > noticed the fields IvyRepResolver.DEFAULT_IVYPATTERN and > IvyRepResolver.DEFAULT_IVYROOT are unused. Should they be removed? The > latter points to what appears to be an abandoned domain as the page is > filled with adds and a link stating "Buy this domain". > > Thanks, > Ben > > -- > about.me/benmccann >
