You mean once you've done sbt coverage, subsequent calls to sbt test produce output? If so, do a sbt clean compile and it should be gone.

No, I mean if I'm running an sbt console (i.e. I run sbt with no task), if I execute the coverage task in that console session, then from that point on, compiling generates instrumented classes.

Ah right. That's because it sets a variable. I think we could add a
"coverageoff" one that does the opposite.

On 5 June 2015 at 23:13, Greg Symons [email protected] wrote:

No, I mean if I'm running an sbt console (i.e. I run sbt with no task),
if I execute the coverage task in that console session, then from that
point on, compiling generates instrumented classes.

—
Reply to this email directly or view it on GitHub
#109 (comment)
.

Yep. I just wanted to see what your opinion on fixing it was before I dove in and did it. I'll go ahead and add coverageoff task and have a PR ready shortly.

1.2.0 released.