Build for Scala 2.11
chrisbeach opened this issue · comments
Please could you release a build for Scala 2.11?
@agrewal @pankajgupta Do you think we can move to 2.10/2.11 now?
I can do this.
It is already for 2.10. Yes 2.11 is outstanding.
On 18-Dec-2014 2:17 pm, "Szymon" notifications@github.com wrote:
@agrewal https://github.com/agrewal @pankajgupta
https://github.com/pankajgupta Do you think we can move to 2.10/2.11
now?—
Reply to this email directly or view it on GitHub
#90 (comment).
@agrewal @pankajgupta We miss the Twitter Ostrich for 2.11. Do you happen to know if we can expect it in the near future? @travisbrown maybe you know?
IIUC, Finagle had a similar problem and excluded subprojects that depend on Ostrich. See https://github.com/twitter/finagle/blob/master/project/Build.scala.
@szymonm Ostrich for 2.11 isn't released yet, but it's available in the develop branch and should be up on Maven Central soon (next week, I'd guess, but I can't promise).
@travisbrown Thanks, that's great. Btw. what's the problem with specs2 and 2.11?
@szymonm Projects like Finagle were on specs (without the "2"), which isn't available for 2.11, and instead of moving to specs2 (which would require extensive changes for some projects), we decided to move all Twitter Scala projects directly to ScalaTest (with a specifically restricted use of the API).
@travisbrown Thanks for your clarification.
So we have the same problem here. We will have to move all spec complaint tests to ScalaTest before going to 2.11. Any volounteers or ideas?
@AnishShah Are you currently working also on 2.11? If not, I can take care of it.
First we need to migrate from ostrich to metrics right? Currently doing
that..
On 21 Jan 2015 02:37, "Szymon" notifications@github.com wrote:
@AnishShah https://github.com/AnishShah Are you currently working also
on 2.11? If not, I can take care of it.—
Reply to this email directly or view it on GitHub
#90 (comment).
Right, ok.
This is now done through a combination of commits 9135d0d