-
Notifications
You must be signed in to change notification settings - Fork 579
publish for Scala 2.12.0-RC1? #174
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
Comments
Thanks @SethTisue. I'll see about getting those patches incorporated. |
Resolves name clash of private[this] var with protected def
Ok so adriaanm@17625f4 got sorted out in 90f2180 And a patch for adriaanm@2bb041a is on its way. Thanks again for the heads up. |
Cool. The fix for adriaanm@2bb041a just got merged internally and will get pushed to the |
Problem / Solution #174 noted that `c.t.concurrent.ConcurrentMultiMap` does not work with Scala 2.12 due to extending `Tuple2`. This uses the suggested workaround of extending `Product2`. RB_ID=873604
the Scala 2.12 community build now tracks your develop branch, as of scala/community-build#307 you might still like to publish artifacts for 2.12.0-RC1? |
thanks! @mosesn, looks like we should move to 2.12.0-RC1 |
👍 yeah, I'm hoping to get to it next week. tried a couple weeks ago but some of our deps weren't publishing for it yet. |
@SethTisue jsyk, right now we're blocked on upgrading scalatest to 3.x internally, since it looks like they've stopped publishing 2.x versions for 2.12. If the migration is painful, we might lobby scalatest to temporarily start publishing 2.x versions again. |
that might be easier now that Scala 2.12.0 JARs are on Maven Central |
We've leaned in on the scalatest |
Looking forward to the release of twitter/util for 2.12.0. |
@jcrossley and others have been working on this and it looks like it should be ready real soon now. |
over at scala/community-build#399 I'm seeing
|
@SethTisue we haven't changed anything in Config in a very long time, so I'm a little suspicious. |
well, this is on a recently nightly of Scala 2.12.1. offhand, it looks like it might have to do with it's certainly possible there's been some regression on our end, but I'd need your help to determine that; I can't afford to go independently investigating in a totally unfamiliar codebase |
the specific nightly used was |
@SethTisue @mosesn I'll look into that. Let me try to reproduce that locally first. |
ok i can reproduce this locally. added this to
And then run:
|
@SethTisue i merged a workaround and hopefully that fixes it. i didn't spend long digging into the difference in the generated code between 2.11, as this |
Problem As reported in #174 new versions of Scala 2.12 changed the behavior of what Config.missingValues sees. Config is deprecated, long in the tooth, a bit finnicky, and generally unsupported by us. Solution Make some patches to the tests to loosen the constraints and also document that the behavior is not perfect in 2.12. RB_ID=895199
perhaps useful, Adriaan's changes to make it work in the Scala 2.12 community build:
The text was updated successfully, but these errors were encountered: