Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compatibility with ScalaCheck 1.11.0 #181

Closed
SethTisue opened this issue Nov 6, 2013 · 11 comments
Closed

compatibility with ScalaCheck 1.11.0 #181

SethTisue opened this issue Nov 6, 2013 · 11 comments

Comments

@SethTisue
Copy link
Contributor

@SethTisue SethTisue commented Nov 6, 2013

when I try to use ScalaTest 2.0 and ScalaCheck 1.11.0 together, I get:

[error] bad symbolic reference. A signature in Configuration.class refers to type Params
[error] in object org.scalacheck.Test which is not available.
[error] It may be completely missing from the current classpath, or the version on
[error] the classpath might be incompatible with the version used when compiling Configuration.class.
[error] one error found
[error] (test:compile) Compilation failed

if I should isolate/minimize this, let me know, I'd be happy to do so.

@bvenners
Copy link
Contributor

@bvenners bvenners commented Nov 6, 2013

Hi Seth,

Sorry, that's been on my list today. Busy day. Rickard made some breaking
changes in the latest release of ScalaCheck. I will attempt to deploy a
SNAP before I have to leave for the train. If not, I'll get it out a bit
later tonight.

Bill

On Tue, Nov 5, 2013 at 4:53 PM, Seth Tisue notifications@github.com wrote:

when I try to use ScalaTest 2.0 and ScalaCheck 1.11.0 together, I get:

[error] bad symbolic reference. A signature in Configuration.class refers to type Params
[error] in object org.scalacheck.Test which is not available.
[error] It may be completely missing from the current classpath, or the version on
[error] the classpath might be incompatible with the version used when compiling Configuration.class.
[error] one error found
error Compilation failed

if I should isolate/minimize this, let me know, I'd be happy to do so.


Reply to this email directly or view it on GitHubhttps://github.com//issues/181
.

Bill Venners
Artima, Inc.
http://www.artima.com

@bvenners
Copy link
Contributor

@bvenners bvenners commented Nov 6, 2013

Hi Seth,

George has deployed a snap release here that is compiled with scalacheck
1.11.0:

https://oss.sonatype.org/content/groups/public/org/scalatest/scalatest_2.10/2.0.1-SNAP/

Please let me know if that works for your projects. I'm flying today but
can do a real release one I have some time to look at the pull request,
hopefully tonight. Be nice to have an external confirmation too.

Thanks.

Bill
On Nov 5, 2013 5:09 PM, "Bill Venners" bill@artima.com wrote:

Hi Seth,

Sorry, that's been on my list today. Busy day. Rickard made some breaking
changes in the latest release of ScalaCheck. I will attempt to deploy a
SNAP before I have to leave for the train. If not, I'll get it out a bit
later tonight.

Bill

On Tue, Nov 5, 2013 at 4:53 PM, Seth Tisue notifications@github.comwrote:

when I try to use ScalaTest 2.0 and ScalaCheck 1.11.0 together, I get:

[error] bad symbolic reference. A signature in Configuration.class refers to type Params
[error] in object org.scalacheck.Test which is not available.
[error] It may be completely missing from the current classpath, or the version on
[error] the classpath might be incompatible with the version used when compiling Configuration.class.
[error] one error found
error Compilation failed

if I should isolate/minimize this, let me know, I'd be happy to do so.


Reply to this email directly or view it on GitHubhttps://github.com//issues/181
.

Bill Venners
Artima, Inc.
http://www.artima.com

@Bohtvaroh
Copy link

@Bohtvaroh Bohtvaroh commented Nov 6, 2013

Just encountered this issue too. 2.0.1-SNAP fixes the problem. Looking forward for a fix in 2.0.1. Thanks.

SethTisue added a commit to NetLogo/NetLogo that referenced this issue Nov 6, 2013
for now this requires a special snapshot build of ScalaTest.
we shouldn't merge this until that has been sorted out.
see scalatest/scalatest#181
@SethTisue
Copy link
Contributor Author

@SethTisue SethTisue commented Nov 6, 2013

thanks Bill. 2.0.1-SNAP works with 1.11.0, but breaks with 1.10.1:

java.lang.NoClassDefFoundError: org/scalacheck/Gen$Parameters$

is the plan that 2.0.1 will require 1.11.0? (that'd be fine with me, not sure about the community at large)

@bvenners
Copy link
Contributor

@bvenners bvenners commented Nov 6, 2013

Hi Seth,

I'm looking at the pull request now. I suspect the problem is that
ScalaCheck 1.11.0 is just plain incompatible with 1.10.x. I doubt I'll be
able to release a version of ScalaTest that works with both. So I'm not
sure when to pull the trigger, but I suspect I should probably pull it
pretty soon. Once I do people who need to use 1.11.0 will have to use an
older version of ScalaTest (such as 2.0 proper). I'll look to see if
there's some way to support both, but it depends on the details of what
broke.

I'll be boarding the plane soon, and will be offline for the duration of
the flight probably. So for the time being I'd suggest folks use 2.0.1-SNAP
for ScalaCheck 1.11.0.

By the way the ScalaTest changes required are here:

https://github.com/scalatest/scalatest/pull/182/files

Looks like some of the old way could have been left deprecated in
ScalaCheck to ease the transition.

Bill

On Nov 6, 2013 11:13 AM, "Seth Tisue" notifications@github.com wrote:

thanks Bill. 2.0.1-SNAP works with 1.11.0, but breaks with 1.10.1:

java.lang.NoClassDefFoundError: org/scalacheck/Gen$Parameters$

is the plan that 2.0.1 will require 1.11.0? (that'd be fine with me, not
sure about the community at large)


Reply to this email directly or view it on GitHub.

@som-snytt
Copy link

@som-snytt som-snytt commented Dec 5, 2013

+1. A mention in the release notes would help save time. And maybe the recommended dependency versions in the sbt snippet.

scalacheck 1.11 removes deprecated API.

I'm not a daily user, but just wanted to try out someone's question on SO. That use case needs a low activation energy. (Just to explain my +1 and not to sound whiny.)

@fractal
Copy link

@fractal fractal commented Jan 20, 2014

when is this going to be released? ScalaTest with PropertyChecks breaks with ScalaTest 2.0, and i definitely want to use the latest version.

@bvenners
Copy link
Contributor

@bvenners bvenners commented Jan 20, 2014

I'm working on getting a 2.1-M1 release out this week. A few more pull requests to merge in and some documentation is all that remains.

@fractal
Copy link

@fractal fractal commented Jan 20, 2014

Thanks!

@bvenners
Copy link
Contributor

@bvenners bvenners commented Feb 14, 2014

This is in 2.1.0-RC2. I am doing the final test on 2.1.0, so will be out soon. Closing this now.

@bvenners bvenners closed this Feb 14, 2014
@SethTisue
Copy link
Contributor Author

@SethTisue SethTisue commented Feb 14, 2014

working for me in 2.1.0-RC2. thanks!

xerial added a commit to msgpack/pickling-msgpack that referenced this issue Feb 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.