Scala 如何指定sbt依赖项以及预期的JDK版本
如何在我的Scala 如何指定sbt依赖项以及预期的JDK版本,scala,maven,sbt,Scala,Maven,Sbt,如何在我的Build.sbt中指定依赖项的JDK版本 我在Aspose库中遇到了这样的情况,其中文件名是用JDK版本后固定的,即Aspose-email-4.8.0-jdk17.jar而不是普通的Aspose-email-4.8.0.jar。因此,通常指定依赖项,例如 "com.aspose" % "aspose-email" % "4.8.0" 将导致sbt投诉以下错误,因为较差的sbt尝试下载不存在的文件: [warn] [FAILED ] com.aspose#aspose-e
Build.sbt
中指定依赖项的JDK版本
我在Aspose库中遇到了这样的情况,其中文件名是用JDK版本后固定的,即Aspose-email-4.8.0-jdk17.jar
而不是普通的Aspose-email-4.8.0.jar
。因此,通常指定依赖项,例如
"com.aspose" % "aspose-email" % "4.8.0"
将导致sbt投诉以下错误,因为较差的sbt尝试下载不存在的文件:
[warn] [FAILED ] com.aspose#aspose-email;4.8.0!aspose-email.jar: (0ms)
[warn] ==== local: tried
[warn] /Users/developer/.ivy2/local/com.aspose/aspose-email/4.8.0/jars/aspose-email.jar
[warn] ==== public: tried
[warn] https://repo1.maven.org/maven2/com/aspose/aspose-email/4.8.0/aspose-email-4.8.0.jar
[warn] ==== Aspose: tried
[warn] http://maven.aspose.com/artifactory/simple/ext-release-local/com/aspose/aspose-email/4.8.0/aspose-email-4.8.0.jar
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: FAILED DOWNLOADS ::
[warn] :: ^ see resolution messages for details ^ ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.aspose#aspose-email;4.8.0!aspose-email.jar
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
sbt.ResolveException: download failed: com.aspose#aspose-email;4.8.0!aspose-email.jar
更新
然后我想,将JDK版本附加到版本号可能会解决这个问题:
"com.aspose" % "aspose-email" % "4.8.0-jdk17"
不幸的是,由于SBT认为POM文件位于aspose-email-4.8.0-jdk17.POM
,而应该是aspose-email-4.8.0.POM
,这将导致另一个错误
[info] Resolving com.aspose#aspose-email;4.8.0-jdk17 ...
[warn] module not found: com.aspose#aspose-email;4.8.0-jdk17
[warn] ==== local: tried
[warn] /Users/ganeshwara/.ivy2/local/com.aspose/aspose-email/4.8.0-jdk17/ivys/ivy.xml
[warn] ==== public: tried
[warn] https://repo1.maven.org/maven2/com/aspose/aspose-email/4.8.0-jdk17/aspose-email-4.8.0-jdk17.pom
[warn] ==== Aspose: tried
[warn] http://maven.aspose.com/artifactory/simple/ext-release-local/com/aspose/aspose-email/4.8.0-jdk17/aspose-email-4.8.0-jdk17.pom
[info] Resolving net.sf.proguard#proguard-base;5.1 ...
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.aspose#aspose-email;4.8.0-jdk17: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] Note: Unresolved dependencies path:
[warn] com.aspose:aspose-email:4.8.0-jdk17 (/Users/ganeshwara/DropMyEmail/backup-server/project/Build.scala#L290)
[warn] +- Dropmysite:common_2.11:1.0-296020c84e74fa1fd65cd5361b563519ff9c4a5d
sbt.ResolveException: unresolved dependency: com.aspose#aspose-email;4.8.0-jdk17: not found
我想如果你仔细研究一下,你会发现问题是由于不同的命名约定造成的——jarfile是用预期的JDK版本发布的,而POM文件不是。在谷歌搜索之后,我发现Maven实际上有一个可选的额外坐标,分类器,它附加在版本号()之后 要在sbt中使用它,您应该将依赖项定义为
"com.aspose" % "aspose-email" % "4.8.0" classifier "jdk17"
()@lolski你从哪里得到这种依赖?在maven centralIt上更具体地说,