Hi David, this is definitely an error on our side which might be caused by the latest changes to the project structure (removing flink-staging directory). I’ve filed a JIRA issue https://issues.apache.org/jira/browse/FLINK-3241. It should be fixed soon.
In the meantime it should work if you build yourself the Flink binaries from the sources. First check them out, then call tools/change-scala-version.sh 2.11 in the root directory and then mvn clean install -DskipTests -Dmaven.javadoc.skip=true. These binaries should depend on the right Scala version. Cheers, Till On Thu, Jan 14, 2016 at 11:25 PM, David Kim <david....@braintreepayments.com > wrote: > Hi, > > I have a scala project depending on flink scala_2.11 and am seeing a > compilation error when using sbt. > > I'm using flink 1.0-SNAPSHOT and my build was working yesterday. I was > wondering if maybe a recent change to flink could be the cause? > > Usually we see flink resolving the scala _2.11 counterparts for akka and > scalatest: > > [info] Resolving com.typesafe.akka#akka-actor_2.11;2.3.7 ... > [info] Resolving com.typesafe#config;1.2.1 ... > [info] Resolving com.typesafe.akka#akka-remote_2.11;2.3.7 ...[info] Resolving > org.scalatest#scalatest_2.11;2.2.4 ... > > > > but am seeing it pick up the _2.10 counterparts: > > [info] Resolving com.typesafe.akka#akka-actor_2.10;2.3.7 ...[info] Resolving > com.typesafe.akka#akka-actor_2.10;2.3.7 ... > [info] Resolving com.typesafe#config;1.2.1 ...[info] Resolving > org.scalatest#scalatest_2.10;2.2.2 ... > > > > This ultimately gives us the following compilation error: > > [error] org.scalatest:scalatest _2.10, _2.11 > java.lang.RuntimeException: Conflicting cross-version suffixes in: > org.scalatest:scalatest > at scala.sys.package$.error(package.scala:27) > at sbt.ConflictWarning$.processCrossVersioned(ConflictWarning.scala:46) > at sbt.ConflictWarning$.apply(ConflictWarning.scala:32) > > > > Maybe the latest 1.0-SNAPSHOT build erroneously built with scala 2.10 for > the 2.11 profile? Any guidance appreciated! > > Thanks, > David > >
