-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Clean Up Build To Clear The Path to 2.12 #257
Conversation
Current coverage is 66.14% (diff: 100%)@@ develop #257 diff @@
==========================================
Files 50 50
Lines 1397 1397
Methods 1347 1347
Messages 0 0
Branches 50 50
==========================================
Hits 924 924
Misses 473 473
Partials 0 0
|
organization := "com.twitter", | ||
scalaVersion := "2.11.8", | ||
crossScalaVersions := Seq("2.10.6", "2.11.8"), | ||
scalaVersion := "2.11.8", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duplicate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch
Thanks a ton! As you can see, none of us are sbt experts (we are barely sbt users ;). |
Thanks for taking a stab at this @clhodapp. I was working on enabling 2.12 for bijection but got stuck on some the failing HBase tests (which you've fixed). I'll try and get a review out to turn on 2.12 publishes and get some artifacts out today. |
I'm anxious to see finagle released for Scala 2.12, so I decided to try to help unblock bijection's 2.12 release. This is my attempt to clean up the build, updating it to sbt 0.13.13 and cleaning up deprecated cruft. It was my explicit intention to NOT do anything that would have a binary compatibility impact here (i.e. this does NOT actually enable 2.12 builds for bijection). By keeping things separate, it should be easier to verify if I've broken things with this build refactoring. In theory, this shouldn't change anything about the generated artifacts (modulo maybe some harmless changes to the pom, since I've moved some things off of the gross
pomExtra
and onto conventional sbt settings). I did update build and test dependencies, since those shouldn't affect the released artifacts.I will note that I can't really test that I didn't break the release process, so sorry in advance if this gets merged and then someone has to fix it.