coverage resets a manually set scalaVersion

[fthomas]

With sbt-scoverage 1.3.3 this happens in my project:

> ++2.10.6
[info] Setting version to 2.10.6
[info] Reapplying settings...
[info] Set current project to refined (in build file:/home/frank/data/code/refined/)
> refinedJVM/scalaVersion
[info] 2.10.6
> coverage
[info] Set current project to refined (in build file:/home/frank/data/code/refined/)
> refinedJVM/scalaVersion
[info] 2.11.7

Calling coverage should not change scalaVersion. I first noticed this issue here fthomas/refined#72.

[rorygraves]

Ouch thats nasty.
My sbt foo is a bit weak, the only client code executed is this

  private def toggleCoverage(status:Boolean): State => State = { state =>
    val extracted = Project.extract(state)
    val newSettings = extracted.structure.allProjectRefs map { proj =>
      coverageEnabled in proj := status
    }
    extracted.append(newSettings, state)
  }

Which is setting the coverageEnabled flag for each project to true. I'm guessing there is a misunderstanding of how/what this code is doing.

[fommil]

I understand scala 2.10 support was dropped in scoverage.

[sksamuel]

Yes it was (was always patchy due to range position stuff).

On 8 April 2016 at 07:40, Sam Halliday notifications@github.com wrote:

I understand scala 2.10 support was dropped in scoverage.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#146 (comment)

[fthomas]

This issue is unrelated to the dropped 2.10 support:

> ++2.11.7
[info] Setting version to 2.11.7
[info] Reapplying settings...
[info] Set current project to refined (in build file:/home/frank/data/code/refined/)
> coreJVM/scalaVersion
[info] 2.11.7
> coverage
[info] Set current project to refined (in build file:/home/frank/data/code/refined/)
> coreJVM/scalaVersion
[info] 2.11.8

Just tested this with version 1.3.5.

[travisbrown]

This is fixed in 1.4.0, right?

[gslowikowski]

Right.

[gslowikowski]

Fixed by #186