Incorrect coverage report for multi-module maven builds

[evansnicholas]

Hi, I have closed my pull request and opened up an issue instead.

The problem we have is the following: when using scoverage in a multi-module maven project with dependencies between the sub-modules (such as classes in one module inheriting from classes in another module) coverage reports are incorrect for the project containing the inheriting class. I have put together a very small maven project that illustrates the problem. I cannot upload it here but I can send it to anyone who is interested in having a look at the issue.

I also submitted a potential solution as a pull request, but as Sam pointed out, it is not an optimal solution as it probably does not solve the problem in a multi-threaded build (or worse, it may introduce new issues). The fundamental problem seems to be that the relationships between the modules mean that scoverage writes the coverage data to the wrong directory when testing the submodule containing the inheriting class.

[tmandke]

I have encountered the same issue with sbt multi module project. Here is a link to my simple project that reproduces the bug https://github.com/tmandke/scov-bug

steps

1. git clone git@github.com:tmandke/scov-bug.git
2. run sbt coverage clean test

command fails and if you look at the report example project is not covered. But, if you look at example/src/main/scala/org/wierdness/example/BarSpec.scala it is covered.

[tmandke]

Reversing the order of the tests in BarSpec.scala makes the issue go away. So, it seems like it depends on what line of code it covered first the parent project or the child.