-
-
Notifications
You must be signed in to change notification settings - Fork 353
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
Scoverage: Issue when also using BuildInfoModule
#640
Comments
@nvander1 ping |
I was wondering, if we could define just the ScoverageTest as additional Test object in a regular ScalaModule, or even as a sub-module of a test module. That way, we could reuse almost all configuration easily. Usage outline: object core extends ScalaModule with ... {
object test extends Tests with ScoverageTests {
def scoverageVersion = "1.3.1"
}
} |
Or in case, one wants to run tests also without scoverage instrumentations: object core extends ScalaModule with ... {
object test extends Tests { }
object scoverage extends Tests with ScoverageTests {
def scoverageVersion = "1.3.1"
}
} |
@lefou I am also experiencing similar issues of missing targets. Feels similar to part 1 of issue #613 as referenced in fulcrumgenomics/commons#47. Also similar to #620 . I'll be looking more in depth at this later this week. |
PR coming later today for this. @lefou |
When I add
ScoverageModule
to a project, that also uses theBuildInfo
module to genrate aBuildInfo.scala
file, the file generator is not properly invoked.The compile step fails, because there is no generated
BuildInfo.scala
.Here is the target execution plan with scoverage:
Add here is the normal plan without scoverage:
At a first glace, one can see the plans are very different. The
core.generatedBuildInfo
target is missing. Also, there are other (essentially) targets missing in this specific case, e.g.GitSupport.publishVersion
which generates thecore.publishVersion
.The text was updated successfully, but these errors were encountered: