[
https://issues.apache.org/jira/browse/BUILDR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646896#action_12646896
]
Alex Boisvert commented on BUILDR-210:
--------------------------------------
I've had success using recent versions of both ScalaCheck and Specs that I've
built manually. My my build.yaml, I use:
[EMAIL PROTECTED] more build.yml
scala.specs: 1.3.2-SNAPSHOT
scala.check: 1.4-scSNAPSHOT
To reference locally-installed snapshots. I'm waiting for both of these
frameworks to release stable and compatible versions for Scala 2.7.2 before
upgrading.
alex
> Hard-Coded ScalaCheck Version Broken in Scala 2.7.2
> ---------------------------------------------------
>
> Key: BUILDR-210
> URL: https://issues.apache.org/jira/browse/BUILDR-210
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Reporter: Daniel Spiewak
> Priority: Blocker
> Fix For: 1.3.4
>
>
> With the release of Scala 2.7.2, the *hard-coded* ScalaCheck version (1.3) is
> no longer sufficient. This version of ScalaCheck depends upon a method which
> no longer exists within the Scala standard library. For the sake of Google,
> this is the precise error message:
> Exception "java.lang.NoSuchMethodError:
> scala.Stream$cons$.apply(Ljava/lang/Object;Lscala/Function0;)Ljava/lang/Object;"
> raised on argument generation.
> The solution is to use ScalaCheck 1.4 instead of 1.3. Just to make things
> even more fun, Specs 1.3.1 does not work with ScalaCheck 1.4 (only with 1.3
> and earlier). This problem is fixed in the (still forthcoming) 1.3.2
> release, but until then, there will apparently be no running tests under
> Scala 2.7.2 using Specs and ScalaCheck in conjunction. Sucks to be me...
> This is an absolute killer for me. I use ScalaCheck quite extensively, which
> means that I now have 300+ tests which now crash where before they ran fine.
> If we can't get a release which either increments the hard-coded version or
> provides a configurable option, could we at least get a patch which can be
> applied manually to do the same?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
