[
https://issues.apache.org/jira/browse/BEAM-6301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734387#comment-16734387
]
Kenneth Knowles commented on BEAM-6301:
---------------------------------------
My reading of https://docs.gradle.org/current/userguide/jacoco_plugin.html was
that {{jacocoTestReport}} should depend on {{test}} automatically. It is OK if
it does not, and we have to set it up. With our complexities it might be
necessary to get weird anyhow - for example, the coverage of {{sdks/java/core}}
depends on {{runners/direct-java:needsRunnerTests}} and each other runner's
ValidatesRunner tests has to be depended upon. We might need a few different
reports from Jacoco.
I actually don't have a strong opinion, except that I want to make these
numbers visible somehow. Even just wiki docs on the invocations could be enough.
> gradle jacoco config is broken
> ------------------------------
>
> Key: BEAM-6301
> URL: https://issues.apache.org/jira/browse/BEAM-6301
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Major
>
> This should run tests and generate a coverage report:
> {code}
> ./gradlew jacocoCoverageReport
> {code}
> But the task does not cause tests to run. It is likely due to the ordering or
> organization inside BeamModulePlugin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
