Logback依赖关系阻止SBT脱机运行

Question

这是对前一个问题的一种改进，并将其更紧密地归因于问题。

我正在确认我可以脱机运行我的SBT项目。我可以，除非登录是我的libraryDependencies之一。为什么登录触发了一个问题？我做了一个简单的例子，包括一个build.sbt和一个“你好世界”的应用程序.

build.sbt通过一系列随机依赖来证明这一点：

name := "testProject"

version := "0.0.1"

scalaVersion := "2.10.3"

libraryDependencies ++= Seq(
    "org.apache.commons" % "commons-math3" % "3.2",
    "com.amazonaws" % "aws-java-sdk" % "1.4.0.1",
    "ch.qos.logback" % "logback-classic" % "1.1.1",
    "com.typesafe.akka" %% "akka-actor" % "2.3.1", 
    "com.typesafe.akka" %% "akka-remote" % "2.3.1",
    "org.scalaz" %% "scalaz-core" % "7.0.3"
)

我的脚步

1. 删除项目中的~/.ivy2、~/.sbt和target/，以确保
2. 确保连接到互联网，并执行sbt run。我的世界跑得很成功
3. 与互联网断开
4. sbt clean
5. sbt run。生成失败，因为logback是一个未解决的依赖项。
6. 再次删除logback依赖项和sbt run。你好，世界运行。

这是步骤5中的错误：

[info] Resolving ch.qos.logback#logback-classic;1.1.1 ...
[warn] Host repo1.maven.org not found. url=http://repo1.maven.org/maven2/ch/qos/logback/logback-classic/1.1.1/logback-classic-1.1.1.pom
[info] You probably access the destination server through a proxy server that is not well configured.
[warn]  module not found: ch.qos.logback#logback-classic;1.1.1
[warn] ==== local: tried
[warn]   /home/user/.ivy2/local/ch.qos.logback/logback-classic/1.1.1/ivys/ivy.xml
[warn] ==== public: tried
[warn]   http://repo1.maven.org/maven2/ch/qos/logback/logback-classic/1.1.1/logback-classic-1.1.1.pom
[info] Resolving org.fusesource.jansi#jansi;1.4 ...
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: ch.qos.logback#logback-classic;1.1.1: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
sbt.ResolveException: unresolved dependency: ch.qos.logback#logback-classic;1.1.1: not found

更新：

使用SBT中的last命令，有很多用于解决依赖关系的调试信息。下面是Akka成功解析的一个例子：

[info] Resolving com.typesafe.akka#akka-actor_2.10;2.3.1 ...
[debug] sbt-chain: Checking cache for: dependency: com.typesafe.akka#akka-actor_2.10;2.3.1 {compile=[default(compile)]}
[debug] sbt-chain: module revision found in cache: com.typesafe.akka#akka-actor_2.10;2.3.1
[debug]     local: revision in cache: com.typesafe.akka#akka-actor_2.10;2.3.1
[debug]     found com.typesafe.akka#akka-actor_2.10;2.3.1 in sbt-chain
[debug] == resolving dependencies testproject#testproject_2.10;0.0.1->com.typesafe.akka#akka-actor_2.10;2.3.1 [compile->runtime]
[debug] == resolving dependencies testproject#testproject_2.10;0.0.1->com.typesafe.akka#akka-actor_2.10;2.3.1 [compile->compile]
[debug] == resolving dependencies com.typesafe.akka#akka-actor_2.10;2.3.1->org.scala-lang#scala-library;2.10.3 [compile->master(*)]
[debug] == resolving dependencies com.typesafe.akka#akka-actor_2.10;2.3.1->org.scala-lang#scala-library;2.10.3 [compile->compile(*)]
[debug] == resolving dependencies com.typesafe.akka#akka-actor_2.10;2.3.1->com.typesafe#config;1.2.0 [compile->master(*)]

以下是Logback的失败：

[info] Resolving ch.qos.logback#logback-classic;1.1.1 ...
[debug] sbt-chain: Checking cache for: dependency: ch.qos.logback#logback-classic;1.1.1 {compile=[default(compile)]}
[debug]         tried /home/user/.ivy2/local/ch.qos.logback/logback-classic/1.1.1/ivys/ivy.xml
[debug]     local: no ivy file found for ch.qos.logback#logback-classic;1.1.1
[debug]         tried http://repo1.maven.org/maven2/ch/qos/logback/logback-classic/1.1.1/logback-classic-1.1.1.pom
[warn] Host repo1.maven.org not found. url=http://repo1.maven.org/maven2/ch/qos/logback/logback-classic/1.1.1/logback-classic-1.1.1.pom
[info] You probably access the destination server through a proxy server that is not well configured.
[debug]     public: no ivy file found for ch.qos.logback#logback-classic;1.1.1
[warn]  module not found: ch.qos.logback#logback-classic;1.1.1
[warn] ==== local: tried
[warn]   /home/user/.ivy2/local/ch.qos.logback/logback-classic/1.1.1/ivys/ivy.xml
[warn] ==== public: tried
[warn]   http://repo1.maven.org/maven2/ch/qos/logback/logback-classic/1.1.1/logback-classic-1.1.1.pom

我可以在缓存中确认以下文件(不是‘~/..ivy/local’文件夹)：

~/.ivy2/cache/ch.qos.logback/logback-classic$ ls
ivy-1.1.1.xml  ivy-1.1.1.xml.original  ivydata-1.1.1.properties  jars

Answer 1

当我尝试它时，这个文件确实是从~/. it 2/cache解析的。我没有本地的，因为我没有在本地出版。您是否可能有一个ivysettings.xml文件(在Linux上，尝试使用locate ivysettings.xml)来处理一些常春藤缓存属性，比如resolutionCacheDir？你为什么只对那个罐子有问题还是个谜.

更新:这似乎是SBT 0.13.1中的一个回归；它在0.13.0中起作用，正如OP自己发现的(见他的答案)，它在0.13.2中得到了修正。

Answer 2

它在你当地的常春藤缓存中找不到它，修复它，你就解决了你的问题。

试着清理你的常春藤缓存，也许它是腐败的。

Answer 3

SBT 0.13.2在这个问题三天后发布，似乎解决了这个问题。我不知道这是否是已知的问题，但是为SBT 0.13.2列出的更改包括

修正常春藤的.+依赖范围未正确转换为maven的问题。