-
Notifications
You must be signed in to change notification settings - Fork 37
Scala 2.12 #49
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
Scala 2.12 #49
Conversation
update to use scala 2.11 with finagle 6.41 and then scalamock-scalatest-support 3.4.2. This needs to wait until patchless has been updated to 2.12 (which I have an open pr to do jeremyrsmith/patchless#2 )
|
Could maintainers merge this PR and release new version? Thanks! |
|
@mxl I haven't had a chance to figure out why tests are failing for 2.12 (seems to be a deadlock since tests just hang after completing) |
|
Potentially (but not necessarily) relevant is the fact that the following is printed under 2.12 but not 2.11: See also https://groups.google.com/forum/#!topic/finaglers/rjAKtJVwaS8 |
|
FWIW, you do get that warning but you don't get the deadlock if tut is disabled. |
|
In fact, you can look at the generated tut markdown files and see that it is getting stuck the first time it comes across a lambda. Perhaps related to http://scala-lang.org/news/2.12.0#object-initialization-locks-and-lambdas. Putting this in |
|
@clhodapp could you open a pr against this branch with your tut fix? |
|
@jeremyrsmith Could you make a new release with Scala 2.12 support? |
|
@jeremyrsmith do you have plans to push the new release to maven central? Is there something we could help with? We're waiting for it to release quill for 2.12. |
|
2.12.2 was just released, which may solve the problem @jeremyrsmith @mxl @fwbrasil http://www.scala-lang.org/news/releases-1Q17.html |
Scala 2.12 support (thanks @cripsywalrus!)