Incorrect gradle project analysis on multi-module projects when subprojects have the same name

[ologe]

I'm playing with Kover (v0.5.0) these days and I noticed a weird behaviour on multi-module projects with a nested hierarchy. When there are submodules with the same name, Kover often analyses the wrong project.

Given the following project structure:

:feature
  :first
  :another-nesting
     :first
     :second
  :nested
     :first
     :second

./gradlew :feature:first:koverHtmlReport is analyzing :feature:nested:first

./gradlew :feature:nested:first:koverHtmlReport is correct

./gradlew :feature:another-nesting:first:koverHtmlReport is analyzing again :feature:nested:first

---

Zero configuration from my side, just applied the plugin.

Downgraded to v0.4.4 and everything works fine.

Everything should be reproducible in this repo https://github.com/ologe/kover-testing

[shanshin]

Hi,
currently, the plugin uses only a short project name.
We will take this issue into account when designing the new API.

[shanshin]

Relates #19

[charlesng]

@shanshin Is there any workaround or release plan for this fix? In my project we used multi module arch and it hurts a lot on the coverage report because of this 😢

[driver733]

@shanshin Is there any workaround or release plan for this fix? In my project we used multi module arch and it hurts a lot on the coverage report because of this 😢

It's probably related to the way Gradle works, that is, it treats different submodules with the same name as the same dependency.

See gradle/gradle#16885