-
Notifications
You must be signed in to change notification settings - Fork 159
Feature request: Scala 2.12 support #126
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
Will definitely come once 2.12 is a bit more stable I think. The reason why is that the AST that the compiler generates might not be locked down yet and that's what the scoverage plugin has to manipulate. |
Can I bump this ... it's a blocker for shapeless adding support for Scoverage because our build matrix includes 2.12.0-M3 and there doesn't appear to be any straightforward way to load it for a subset of Scala versions. |
scoverage/scalac-scoverage-plugin#152 |
Gotcha ... thanks. |
@sksamuel We are trying to add scoverage to milessabin/shapeless and are currently blocked because current version of plugin always tries to load scala version specific runtime plugins. I see that this is fixed in master but there is no version released. Any plans to release it soon? Btw, sorry about double posting, but it's been a few days already https://groups.google.com/forum/#!topic/scala-code-coverage-tool/OUiAS1EVmcQ |
If its just a release you need I can do it later today.
|
I would like to test it before release. It's not even merged to master and you commented a week ago that there are still failing tests. Has something changed since then? |
I think he's talking about the other issue, not 2.12 support, just happens On 6 March 2016 at 10:40, Grzegorz Slowikowski notifications@github.com
|
If it' about #153, your commit broke |
Any news on this? |
As Scala 2.12.0 was officially released today, do you have a schedule for releasing a compatible version of scoverage? (Thanks for providing such a great tool, BTW!) |
Version |
👍 thanks |
The title says it all, I think :-)
The text was updated successfully, but these errors were encountered: