specs2, sbt 0.12 and scala 2.9.1

60 views
Skip to first unread message

Robin Green

unread,
Feb 20, 2013, 4:31:04 AM2/20/13
to simple-b...@googlegroups.com
I can't run my specs2 tests on scala 2.9.1, with or without fork := true, from sbt 0.12.0, because I keep getting IncompatibleClassChangeError. Unfortunately the IncompatibleClassChangeError doesn't specify which class it's talking about, and many people have reported this error in connection with sbt in the past. I suspect that in my case this is related to the following classpath entry:

/home/robin/.sbt/boot/scala-2.9.2/org.scala-sbt/sbt/0.12.0/test-agent-0.12.0.jar

which presumably is compiled against Scala 2.10?

The reason I tried to switch to sbt 0.12.0 was to use (a derivative of) sbt-native-packager, which is no longer available for sbt 0.11.3.

Robin Green

unread,
Feb 20, 2013, 4:58:15 AM2/20/13
to simple-b...@googlegroups.com
Ah, no, should have looked more closely - it looks like it's compiled against 2.9.2, and anyway test-interface is probably the more likely culprit. What's particularly galling about this is:

(a) the "bad"-looking test interface jar is not on the test:full-classpath - so full-classpath is a misnomer
(b) another version of it, presumably the correct version which specs2 already depends on anyway, IS on the full-classpath!

So it looks like I just need to figure out how to rip out the offending duplicate jar for test-interface.

Robin Green

unread,
Feb 20, 2013, 5:20:11 AM2/20/13
to simple-b...@googlegroups.com
(oops, posted with wrong email address just now)

No, it can't be the duplicate test-interface jar - it is byte-for-byte identical to the other jar. Must be something else.

Robin Green

unread,
Feb 20, 2013, 5:49:37 AM2/20/13
to simple-b...@googlegroups.com
Sorry for the noise - it appears to be due to other dependencies not being updated for an incompatible specs2 change between snapshots, and entirely unrelated to my move to sbt 0.12.0.
Reply all
Reply to author
Forward
0 new messages