-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error "Kover plugin not applied in projects" when there are nested subproject #222
Comments
Hi, |
|
At the moment, the Kover plugin assumes an explicit applying in each of the projects. To exclude an intermediate project from checking, try writing in the aggregating project something like
|
Note that the fix in #224 is more of a hack than a fix. Really it should be removed and replaced with something like this: https://docs.gradle.org/7.3/samples/sample_jvm_multi_project_with_code_coverage.html |
Fixed in |
If I have a Gradle project where there are subprojects nested inside empty directories, then Gradle considers these directories to be subprojects, but they are not.
Here Gradle considers
:subprojects
to be a subproject, and so does Kover, but it should be ignored.This can be set manually, but it would be nicer if this wasn't necessary. I think the solution to this is to use variant aware sharing: https://docs.gradle.org/7.5.1/userguide/cross_project_publications.html
Here's a demo from Gradle: https://docs.gradle.org/7.3/samples/sample_jvm_multi_project_with_code_coverage.html
The text was updated successfully, but these errors were encountered: