Note that there are some explanatory texts on larger screens.

plurals
  1. POSBT doesn't seem to download transitive dependencies with a custom repository?
    text
    copied!<p>I'm new to SBT, using version 1.0 and a custom repository, and I've set the "retrieveManaged" flag mentioned <a href="https://stackoverflow.com/questions/6703292/retrieving-project-dependencies-with-sbt" >here</a>, but it seems that SBT only downloads the directly requested JARs, but not any of the JARs upon which those JARs depend. And yes, the repository is using the customary default format described in the answers <a href="https://stackoverflow.com/questions/4342079/how-can-i-retrieve-snapshot-dependencies-from-nexus-using-sbt" >here</a> (though SBT/Ivy doesn't seem capable of retrieving snapshots, either, but that's a separate problem, I expect). The repository does not require any kind of authentication, FYI.</p> <p>Here's a slightly generified version of my built.sbt file:</p> <pre><code>name := "MyProject" organization := "com.myorg" version := "0.1" scalaVersion := "2.9.0" scalacOptions += "-deprecation" retrieveManaged := true resolvers += Resolver.url("myorg", url("http://host.com//content/groups/public")) libraryDependencies += "com.myorg" % "otherproject" % "1.0" fork in run := true </code></pre> <p>The requested "otherproject" JAR file loads fine, but SBT/Ivy seems to have no interest in opening up its POM and downloading the other JARs it needs to operate. This seems like it should be a fairly basic function (Maven does it, for example) but I have no idea how to convince SBT/Ivy to do so. (And the <a href="https://github.com/harrah/xsbt/wiki/Library-Management" rel="nofollow noreferrer" >documentation assures us</a> that SBT is, in fact, supposed to do this: "By default, these declarations fetch all project dependencies, transitively".)</p> <p>I believe I must be doing something wrong, but have no idea -- given how simple and vanilla this basic configuration is -- what it could be.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload