Skip to content
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

with onCheck.set(true) merged tasks are not launched #213

Closed
AleksDanil opened this issue Aug 18, 2022 · 1 comment · Fixed by #215
Closed

with onCheck.set(true) merged tasks are not launched #213

AleksDanil opened this issue Aug 18, 2022 · 1 comment · Fixed by #215

Comments

@AleksDanil
Copy link

0.6.0-Beta

I configured simple multi module project and set onCheck.set(true) for verify, htmlReport, xmlReport inside koverMerged for parent module:

koverMerged {
    enable()

    xmlReport {
        onCheck.set(true)
    }
    
    htmlReport {
        onCheck.set(true)
    }

    verify {
        onCheck.set(true)
        ...
    }

}

None of koverMergedHtmlReport, koverMergedXmlReport, koverMergeVerify is launched when I run check task.

You can check attached project MultiModule.zip

@shanshin
Copy link
Collaborator

Not a bug, lack of documentation:
onCheck applies only to the check task located in the same project where the merged tasks were created (koverMerged.enable() was called).

In this example, this is the root project. However, because the base plugin is not directly or transitively applied , then the check task does not exist in it and merged reports are not attached to anything.

This is easy to check by calling ./gradlew :check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants