On Sat, Mar 7, 2009 at 10:58 AM, lacton <[email protected]>wrote:
> After not contributing for far too long, I wanted to start working on > some JIRA issues, but I've run into some obstacles and I'd like your > help. > > After updating my working copy, I tried to run 'rake spec' to make > sure I would start coding on a green bar. The command failed because > the script couldn't download org.scalatest:scalatest:jar:0.9.4. > Looking at the http://scala-tools.org/repo-releases maven repo, I > noticed the scalatest artifact was not there. The POM file states > that the artifact was relocated with groupId > "org.scala-tools.testing". It looks like buildr doesn't handle > <relocation> tags in POM files. Until buildr gets this feature, I > think we should use the new groupId for the scalatest artifact (line > 87 in file lib/buildr/scala/tests.rb). What do you think? Yes, I've just updated to the new groupId and upgraded to ScalaTest 0.9.5 in the process. Updating the groupId on my working copy, I was able to run buildr's > specs and I got 7 failures. > > 1) RuntimeError in 'Buildr::Scala::ScalaTest should include public > classes extending org.scalatest.FunSuite' > Tests failed! > > 2) RuntimeError in 'Buildr::Scala::ScalaTest should ignore inner classes' > Tests failed! > > 3) 'Buildr::Scala::ScalaTest should pass when ScalaTest test case passes' > FAILED > expected no Exception, got #<RuntimeError: Tests failed!> > > 4) RuntimeError in 'Buildr::Scala::ScalaTest should report to > reports/scalatest/TEST-TestSuiteName.txt' > Tests failed! > > 5) RuntimeError in 'Buildr::Scala::ScalaTest should pass properties to > Suite' > Tests failed! > > 6) RuntimeError in 'Buildr::Scala::ScalaTest should compile and run > specifications with "Specs" suffix' > Tests failed! > > 7) RuntimeError in 'Buildr::Scala::ScalaTest should run with > ScalaCheck automatic test case generation' > Tests failed! > > Do you have these failures too, or is my environment broken? The specs run fine here. Are you testing with Scala 2.7.3? Did you set SCALA_HOME to point to the base of the Scala 2.7.3 distribution? I've been meaning to add a precondition to the specs so they fail early and explicitly if the Scala version doesn't match what is expected. I'll get on it. alex
