Scala 2.11 + Neo4j - Cypher 编译器的成熟依赖

Question

我想升级我的 Scala项目至 2.11.1语言版本。

当我更新我的 build.sbt文件并尝试编译我得到的项目

[error] Modules were resolved with conflicting cross-version suffixes in {file:somePathTo}SomeProject:
[error]    org.parboiled:parboiled-scala _2.11, _2.10
java.lang.RuntimeException: Conflicting cross-version suffixes in: org.parboiled:parboiled-scala
    at scala.sys.package$.error(package.scala:27)
    at sbt.ConflictWarning$.processCrossVersioned(ConflictWarning.scala:47)
    at sbt.ConflictWarning$.apply(ConflictWarning.scala:30)
    at sbt.Classpaths$$anonfun$60.apply(Defaults.scala:1090)
    at sbt.Classpaths$$anonfun$60.apply(Defaults.scala:1090)
    at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
    at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:42)
    at sbt.std.Transform$$anon$4.work(System.scala:64)
    at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237)
    at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237)
    at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:18)
    at sbt.Execute.work(Execute.scala:244)
    at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237)
    at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237)
    at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:160)
    at sbt.CompletionService$$anon$2.call(CompletionService.scala:30)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
[error] (*:update) Conflicting cross-version suffixes in: org.parboiled:parboiled-scala

起初我认为这是因为我对 Spray 的依赖库也依赖于 parboiled所以我在他们的用户列表上发布了一个问题: https://groups.google.com/forum/#!topic/spray-user/XY7ceh7a9t0他们建议我尝试查看我的项目的依赖关系图。

看来，parboiled 不仅被 Spray 使用库，但也由 Cypher 编译器(我依赖于 Spraing Data Neo4j )。

两者 2.0和 2.1版本正在使用 parboiled用于 Scala 2.10 .

http://mvnrepository.com/artifact/org.neo4j/neo4j-cypher-compiler-2.0/2.0.3
http://mvnrepository.com/artifact/org.neo4j/neo4j-cypher-compiler-2.1/2.1.2

我想知道是否有可能/被认为是安全的删除此版本的传递依赖 parboiled库 ( http://www.scala-sbt.org/0.13.5/docs/Detailed-Topics/Library-Management.html#exclude-transitive-dependencies ) 并添加 2.11到我的类路径。

如果有人来自 Neo4j，我将不胜感激团队可以判断是否有任何计划发布针对 parboiled 编译的 Cypher 编译器版本。适用于 Scala 2.11 .

只是为了完整性，这里是我的 build.sbt 的依赖部分:

libraryDependencies ++= Seq(
  "com.typesafe.akka" %% "akka-actor" % AkkaVersion,
  "com.typesafe.akka" %% "akka-slf4j" % AkkaVersion,
  "com.typesafe.akka" %% "akka-testkit" % AkkaVersion % "test",
  "com.typesafe.akka" %% "akka-persistence-experimental" % AkkaVersion,
  "io.spray" %% "spray-can" % SprayVersion,
  "io.spray" %% "spray-routing" % SprayVersion,
  "io.spray" %% "spray-testkit" % SprayVersion % "test",
  "io.spray" %% "spray-json" % SprayJsonVersion,
  "ch.qos.logback" % "logback-classic" % LogbackVersion,
  "org.specs2" %% "specs2" % Specs2Version,
  "org.springframework.data" % "spring-data-neo4j" % SDNVersion,
  "org.springframework.data" % "spring-data-neo4j-rest" % SDNVersion,
  "javax.validation" % "validation-api" % ValidationAPIVersion,
  "com.github.nscala-time" %% "nscala-time" % NscalaTimeVersion,
  "org.neo4j" % "neo4j-kernel" % Neo4jVersion % "test" classifier "tests",
  "org.mockito" % "mockito-all" % MockitoVersion,
  "com.typesafe.scala-logging" %% "scala-logging" % ScalaLoggingVersion,
  "io.kamon" %% "kamon-core" % KamonVersion,
  "io.kamon" %% "kamon-spray" % KamonVersion,
  "io.kamon" %% "kamon-statsd" % KamonVersion,
  "org.aspectj" % "aspectjweaver" % AspectjVersion
)

Answer 1

肯定有计划更新到更新版本的 Scala 并更新依赖项，例如 parboiled。然而，Neo4j 作为一个复杂的数据库系统，具有大量的依赖关系，任何这种性质的改变都需要在迁移和测试方面付出巨大的努力。因此，目前没有可用于此类更改的 ETA。