冲突的跨版本后缀（sbt，Scala-STM，Play-JSON） [英] Conflicting cross-version suffixes (sbt, Scala-STM, Play-JSON)

问题描述

我使用的是JSON扩展，该扩展依赖于Mandubian的play-json 2.2-SNAPSHOT。到目前为止一切正常，直到我有了一个基于Scala-STM的项目。 sbt报告以下问题：

I am using a JSON extension which relies on Mandubian's play-json 2.2-SNAPSHOT. Everything worked fine until now I have a project based on Scala-STM. sbt reports the following problem:

[error] Modules were resolved with conflicting cross-version suffixes 
        in {file:folder}project:
[error]    org.scala-stm:scala-stm _2.10, _2.10.0
java.lang.RuntimeException: Conflicting cross-version suffixes in: 
  org.scala-stm:scala-stm

是否有机会更深入地了解这两个冲突的地方版本来自哪里？我很惊讶play-json应该取决于scala-stm吗？！

Is there any chance to dig deeper into where these two "conflicting" versions come from? I am quite surprised that play-json should be depending on scala-stm?!

此外，还有一种方法可以说服sbt关闭...。因为显然是2.10和2.10.0是等效的版本。

Furthermore, is there a way to convince sbt to shut the ... up. Because obviously 2.10 and 2.10.0 are equivalent versions.

编辑：这似乎是sbt 0.13的一个错误（可能与Play-JSON无关），因为如果我恢复到0.12.4，该项目将成功更新和构建。我仍然对sbt 0.13感兴趣。

EDIT: This seems to be an sbt 0.13 bug (and probably has nothing to do with Play-JSON), because if I revert to 0.12.4, the project successfully updates and builds. I am still interested in a work around for sbt 0.13.

推荐答案

您可以通过使用exclude <删除scala-stm来解决此问题。 / p>

You can get around this by removing scala-stm with exclude

 "dependencyGroupId" %% "dependencyArtifactId" % "dependencyVersion" exclude("org.scala-stm", "scala-stm_2.10.0")

别忘了做 sbt清理。

这篇关于冲突的跨版本后缀（sbt，Scala-STM，Play-JSON）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！