Closed r4phab closed 6 months ago
Hi, in version 0.7.5, an additional configuration correctness check was added, so now an error is displayed indicating that the configuration is incorrect.
The uncontrolled using of mergeWith
can lead to unexpected consequences, optionality feature will be implemented in the next version of DSL.
Now you can use the steps described in this comment to specify a more correct configuration.
@shanshin Indeed we updated our configuration following the comment you mentioned and it works now ! Thank you very much for guiding us in the right direction 🥳
Describe the bug A clear and concise description of what the bug is. I have multiple modules, some are JVM only (domain) and others and Android modules. With the latest version
0.7.5
the reports merging with JVM and Android modules is broken. Worked fine in0.7.3
Errors If present, stacktraces or files from
build/kover/errors
directoryExpected behavior Skip the mergedWith instruction if not found in the JVM module ?
Reproducer A link to your project, if it is open source. Otherwise, please try to reproduce the problem on a small project. If this is not feasible, give an example of the code on which the problem manifests itself.
Reports If applicable, report files or screenshots.
Environment
Other context important for this bug: [e.g. OS version] Here is my Kover configuration in Groovy :
koverReport { filters { excludes { classes(koverExcludes) annotatedBy(*koverAnnotationsExcludes) } } defaults { mergeWith("prodRelease")
}