scalatest / sbt question

[Sciss]

hi,

(this is probably more a question for sbt ... ?)

i am not very familiar with the dependancy management of sbt. but i wonder why i need to include scalatest in my project if it depends on ccstm. is scalatest actually used in ccstm or just in ccstm-test?

the question comes up as sbt just refused to sync with the scalatest RC7 snapshot, don't know why. i have changed my entry now to

"org.scalatest" % "scalatest" % "1.2-for-scala-2.8.0.final-SNAPSHOT"

which seems to satisfy sbt. generally, i would think that if my project has dependancy

"Stanford CS - Pervasive Parallelism Laboratory" %% "ccstm" % "0.2"

then why wouldn't sbt automatically include ccstm's dependancies in lib_managed? i find myself (with other libraries as well) needing to include all the dependancies' dependancies as well.

best, -sciss-

[Nathan Bronson]

Sciss,

I'm not an sbt (or maven) expert, but your project shouldn't need a
dependency on scalatest to use CCSTM.

Try using the following two lines for the dependency, and use "sbt
update" to download the CCSTM jar automatically:

val ccstmDep = "edu.stanford.ppl" % "ccstm" % "0.2-for-scala-2.8.0"
val ccstmRepo = "CCSTM Release Repository at PPL" at
"http://ppl.stanford.edu/ccstm/repo-releases"

- Nathan

[Sciss]

hey,

i got it all working now without scalatest.

it was all a bit of a hassle with sbt, until i realized that once you change a dependancy in the project, you really should increase the project build version, because it seems somewhere the ivy.xml files are cached and so follow-up projects get confused and don't necessarily pick up the dependancy changes (despite renewed publish-local / update)... also now i could remove non-immediate dependancies, so all looks as it should. phew...

best, -sciss-

[Nathan Bronson]

Glad to hear you're getting it working the way you want.

Version numbers ending in -SNAPSHOT are special, perhaps that would
prevent the caching that is causing you problems?

- Nathan