Sergey Shanshin
Sergey Shanshin
As part of [the migration of separate BCV functionality to Kotlin Gradle Plugin](https://youtrack.jetbrains.com/issue/KT-71098/Migrate-Binary-Compatibility-Validator-to-Kotlin-Gradle-Plugin), the addition of new features to a separate plugin has been discontinued. This does not look like...
Fixed along with #206
Hi, this is because Kover Gradle Plugin use the [matching](https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/TaskCollection.html#matching-org.gradle.api.specs.Spec-) function to locate test tasks but it is not lazy - it causes the creation of an instance of the...
> But what about using opt-in of other tasks instead to not configure the tasks by default? This can be done, but in this case it is necessary to significantly...
Unfortunately, the `named {}` function in Gradle still contains a [similar error](https://github.com/gradle/gradle/issues/28347), and it causes the creation of all tasks (see [example](https://github.com/gradle/gradle/issues/28347#issuecomment-1980639777)). Therefore, at the moment it is difficult to...
>But I have one question left: How do I setup rules in settings plugin? There is no verify task in settings plugin right now, but I think we will add...
@hfhbd, verification was added in `0.9.0-RC`
> What does the postponed label mean in this case? Hi, please refer to #720. We plan to switch to using the JaCoCo agent, work in this area has been...
Closed due to the end of IntelliJ Agent development (#720) and the introduction of a new strategy for measuring of Kotlin code coverage (#746). It is recommended to use JaCoCo,...
> @shanshin , if it is recommended to use JaCoCo, what is the purpose of Kover? In its current form, this is a trade-off, the two implementations have their drawbacks....