We have a large project which contains many modules/sub projects. Several of these modules add classes into common package names. When we run the emma coverage reports the totals at the top appear to behave as expected (i.e. more unit tests and coverage goes up) but when you click into the package listings only the classes from the last module compiled are shown when there are in fact lots of classes from different modules that should be in the package.

e.g.

module a defines classes in in uk.co.mycompany.common (and other packages)
module b defines classes in in uk.co.mycompany.common (and other packages)

only the classes from module b show in the uk.co.mycompany.common coverage report, but the classes in module a uk.co.mycompany.common seem to affect the totals at the top of the coverage report. The other packages from module a will show correctly (I think).

Each module is generating it's own emma config file (due to our maven setup) so I assume its something to do with the way statistics are combined between files.