Question

我已经下载了SBT（sbt-0.13.15.zip）并将其解压缩，但是在运行sbt.bat时我遇到了问题。

最初，当我发现我需要指定仅 http s 配置而不是http 时，我解决了我修复的代理问题。正在采取http一个，它失败了。

所以现在我不再有代理问题，但是在尝试获取jansi依赖项时失败了：

setting 'basedir' to 'C:\Users\vfuchs070114\.sbt\boot' :: resolving dependencies :: org.scala-sbt#boot-jansi;1.0 confs: [default] validate = true refresh = false resolving dependencies for configuration 'default' == resolving dependencies for org.scala-sbt#boot-jansi;1.0 [default] loadData of org.scala-sbt#boot-jansi;1.0 of rootConf=default == resolving dependencies org.scala-sbt#boot-jansi;1.0->org.fusesource.jansi#jansi;1.11 [default->default(compile)] loadData of org.fusesource.jansi#jansi;1.11 of rootConf=default using redefined-public to resolve org.fusesource.jansi#jansi;1.11 redefined-public: Checking cache for: dependency: org.fusesource.jansi#jansi;1.11 {default=[default(compile)]} redefined-public: no namespace defined: using system no ivy file in cache for org.fusesource.jansi#jansi;1.11: tried C:\Users\vfuchs070114\.ivy2\cache\org.fusesource.jansi\jansi\ivy-1.11.xml redefined-public: no latest strategy defined: using default local: no namespace defined: using system no ivy file in cache for org.fusesource.jansi#jansi;1.11: tried C:\Users\vfuchs070114\.ivy2\cache\org.fusesource.jansi\jansi\ivy-1.11.xml trying C:\Users\vfuchs070114\.ivy2\local\org.fusesource.jansi\jansi\1.11\ivys\ivy.xml tried C:\Users\vfuchs070114\.ivy2\local\org.fusesource.jansi\jansi\1.11\ivys\ivy.xml local: resource not reachable for org.fusesource.jansi#jansi;1.11: res=C:\Users\vfuchs070114\.ivy2\local\org.fusesource.jansi\jansi\1.11\ivys\ivy.xml trying C:\Users\vfuchs070114\.ivy2\local\org.fusesource.jansi\jansi\1.11\jars\jansi.jar tried C:\Users\vfuchs070114\.ivy2\local\org.fusesource.jansi\jansi\1.11\jars\jansi.jar local: resource not reachable for org.fusesource.jansi#jansi;1.11: res=C:\Users\vfuchs070114\.ivy2\local\org.fusesource.jansi\jansi\1.11\jars\jansi.jar local: no ivy file nor artifact found for org.fusesource.jansi#jansi;1.11 local-preloaded-ivy: no namespace defined: using system no ivy file in cache for org.fusesource.jansi#jansi;1.11: tried C:\Users\vfuchs070114\.ivy2\cache\org.fusesource.jansi\jansi\ivy-1.11.xml trying file:/C:/Users/vfuchs070114/.sbt/preloaded/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml tried file:/C:/Users/vfuchs070114/.sbt/preloaded/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml local-preloaded-ivy: resource not reachable for org.fusesource.jansi#jansi;1.11: res=file:/C:/Users/vfuchs070114/.sbt/preloaded/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml local-preloaded-ivy: no ivy file found for org.fusesource.jansi#jansi;1.11 local-preloaded: no namespace defined: using system no ivy file in cache for org.fusesource.jansi#jansi;1.11: tried C:\Users\vfuchs070114\.ivy2\cache\org.fusesource.jansi\jansi\ivy-1.11.xml trying file:/C:/Users/vfuchs070114/.sbt/preloaded/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom tried file:/C:/Users/vfuchs070114/.sbt/preloaded/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom local-preloaded: resource not reachable for org/fusesource/jansi#jansi;1.11: res=file:/C:/Users/vfuchs070114/.sbt/preloaded/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom trying file:/C:/Users/vfuchs070114/.sbt/preloaded/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar tried file:/C:/Users/vfuchs070114/.sbt/preloaded/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar local-preloaded: resource not reachable for org/fusesource/jansi#jansi;1.11: res=file:/C:/Users/vfuchs070114/.sbt/preloaded/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar local-preloaded: no ivy file nor artifact found for org.fusesource.jansi#jansi;1.11 Maven Central: no namespace defined: using system no ivy file in cache for org.fusesource.jansi#jansi;1.11: tried C:\Users\vfuchs070114\.ivy2\cache\org.fusesource.jansi\jansi\ivy-1.11.xml trying https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom tried https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom problem occurred while resolving dependency: org.fusesource.jansi#jansi;1.11 {default=[default(compile)]} with Maven Central: java.lang.RuntimeException: java.util.NoSuchElementException at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1453) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1439) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2965) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:489) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) at org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:130) at org.apache.ivy.util.url.BasicURLHandler.getURLInfo$57a0216e(BasicURLHandler.java:73) at org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) at org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:65) at org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:81) at org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) at org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:96) at org.apache.ivy.plugins.resolver.IBiblioResolver.findIvyFileRef(IBiblioResolver.java:102) at org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:228) at org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:512) at org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:169) at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:714) at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:799) at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:722) at org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:594) at org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:234) at xsbt.boot.Update.xsbt$boot$Update$$lockedApply(Update.scala:105) at xsbt.boot.Update$$anon$4.call(Update.scala:99) at xsbt.boot.Locks$GlobalLock.withChannel$1(Locks.scala:93) at xsbt.boot.Locks$GlobalLock.xsbt$boot$Locks$GlobalLock$$withChannelRetries$1(Locks.scala:78) at xsbt.boot.Locks$GlobalLock$$anonfun$withFileLock$1.apply(Locks.scala:97) at xsbt.boot.Using$.withResource(Using.scala:10) at xsbt.boot.Using$.apply(Using.scala:9) at xsbt.boot.Locks$GlobalLock.ignoringDeadlockAvoided(Locks.scala:58) at xsbt.boot.Locks$GlobalLock.withLock(Locks.scala:48) at xsbt.boot.Locks$.apply0(Locks.scala:31) at xsbt.boot.Locks$.apply(Locks.scala:28) at xsbt.boot.Update.apply(Update.scala:100) at xsbt.boot.Launch.update(Launch.scala:352) at xsbt.boot.Launch$$anonfun$jansiLoader$1.apply(Launch.scala:178) at scala.Option.getOrElse(Option.scala:120) at xsbt.boot.Launch.jansiLoader$2f324eef(Launch.scala:173) at xsbt.boot.Launch.<init>(Launch.scala:150) at xsbt.boot.Launcher$.apply(Launch.scala:366) at xsbt.boot.Launch$.apply(Launch.scala:18) at xsbt.boot.Boot$.runImpl(Boot.scala:41) at xsbt.boot.Boot$.main(Boot.scala:17) at xsbt.boot.Boot.main(Boot.scala) Caused by: java.util.NoSuchElementException at java.util.StringTokenizer.nextToken(StringTokenizer.java:349) at sun.net.www.protocol.http.HttpURLConnection.doTunneling(HttpURLConnection.java:2016) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:183) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1511) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1439) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) ... 41 more

它试图从存在的https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom获取数据，但它似乎无法解析它或其他东西（StringTokenizer抛出的NoSuchElementException）。我试图将pom和jar文件放在本地所在的位置试图找到它们：它找到了它们，但它最终并没有产生很大的不同。
类似的东西发生在typesafe-ivy-releases和sbt-ivy-snapshots上，为此它试图从不存在的远程URL获取一些常春藤信息：

https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml

https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml

因此，在这种情况下，它失败并不是一个重大的惊喜。

任何可能出错的想法？

由于

============

修改

我在这里https://github.com/typesafehub/activator/issues/18看到它可能是Ipv4 / Ipv6的问题。我尝试添加推荐的属性以强制IPv4（-Djava.net.preferIPv4Stack = true），但它仍然无效。

但是，我觉得根本原因可能是这样的，或者某些编码问题，使远程文件“不可解析”

修改2

我昨天花了整整一天手动获取依赖项，最后它还没有工作..然后我在家里的电脑上试了一下，没有代理，它运行得很好。所以现在我再次尝试，专注于运行sbt.bat：我在java调用之前在sbt.bat中添加了一个“echo”，以确保它符合我的预期，并且确实如此：

"C:\Toolbox\apps\jdk\jdk1.8.0_25-windows-x64\bin\java.exe" -Dhttps.proxyHost=theProxyURL -Dhttps.proxyPort=8080 -Dhttps.proxyUser=myId -Dhttps.proxyPassword=myPassword -cp "C:\Toolbox\apps\sbt-0.13.15_2ndTry\bin\sbt-launch.jar" xsbt.boot.Boot

但我仍然遇到问题..如果是证书问题或类似问题，我应该收到更明确的信息，对吧？

编辑3

我观察到的是，即使代理配置不正确，我们也不会在日志中收到任何相关消息。例如，通过故意提供不正确的代理设置（例如，不存在的代理主机），我们得到的消息与配置正确的值时不同。这使得调试非常不方便。

另一个我发现，即使正确配置密码，当密码包含感叹号时，修改后的版本也可能会传递给SBT启动器。我为此创建了一个问题：https://github.com/sbt/sbt/issues/3139。但即使解决了这个问题，我仍然面临着问题。

实际上有几个与代理相关的未解决问题：https://github.com/sbt/sbt/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20proxy

我现在要注意的一件事是配置代理存储库：http://www.scala-sbt.org/0.13/docs/Proxy-Repositories.html（我们使用Nexus）

Answer 1

即使我无法找到最初问题的确切答案，我也学到了一些东西：

在企业互联网代理后面使用SBT的解决方法是使用内部Nexus代理：Why is sbt trying to download non-existing dependencies?
SBT日志记录不是很有帮助，相同的错误消息可能有几十个失败的实际原因。
根据配置的依赖存储库（http://www.scala-sbt.org/0.13/docs/Proxy-Repositories.html），SBT将根据各种命名约定（Ivy和Maven）尝试各种UR。这就是有时URL根本不存在的原因。

Answer 2

如果您支持代理（公司网络）对于Windows：在sbt安装文件夹中，转到conf / sbtconfig.txt文件，只需添加以下行并保存并尝试。

-Dhttp.proxyHost=proxy
-Dhttp.proxyPort=portno
-Dhttp.proxyUser=UserId
-Dhttp.proxyPassword=Password

-Dhttps.proxyHost=proxyhost
-Dhttps.proxyPort=portno 
-Dhttps.proxyUser=UserId
-Dhttps.proxyPassword=Password

对于Linux / Unix：

export JAVA_OPTS="$JAVA_OPTS -Dhttp.proxyHost=proxyHost  -Dhttp.proxyPort=proxyPortNumber -Dhttp.proxyUser=UserId -Dhttp.proxyPassword=Password -Dhttps.proxyHost=proxyHost -Dhttps.proxyPort=proxyPortNumber  -Dhttps.proxyUser=UserId -Dhttps.proxyPassword=Password"

它对我有用。

Answer 3

确保在执行sbt构建的框中没有设置任何代理环境变量（http_proxy, https_proxy等）。以我的经验，如果您将SBT设置为通过https（例如Nexus）从代理存储库下载依赖项并同时设置https_proxy env var，那么对于SBT可能会出现问题。如docs中所述，这些代理设置由SBT自动获取，因此unset https_proxy首先运行sbt构建。

Answer 4

对于那些使用Corporate代理背后的人，并且仍然试图弄清楚如何在IntelliJ中设置HTTP代理的人，这对我很有用。我希望这可以帮助像我这样的IntelliJ新手。

（注意：在相应的框中指定您的网络用户名和密码）：-

首次使用SBT - 检索代理后面的依赖关系

4 个答案: