uber/NullAway

Switch code coverage aggregation to use built-in plugin

Open

#871 创建于 2023年11月29日

在 GitHub 查看
 (1 评论) (0 反应) (1 负责人)Java (3,462 star) (288 fork)batch import
good first issuehelp wanted

描述

Sample: https://docs.gradle.org/current/samples/sample_jvm_multi_project_with_code_coverage_distribution.html we can get rid of a bunch of custom Gradle code by changing the code-coverage-report module to use this built-in aggregating technique.

贡献者指南

技术栈
java
领域
build systemtesting
议题类型
refactor
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
GradleJavacode coverage
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
The issue suggests switching the code coverage report module to use Gradle's built in code coverage aggregation plugin, as shown in the linked Gradle sample. Investigate the current module setup in the repository and compare it with the sample. Look for files like build.gradle or settings.gradle in the code coverage report directory. Consider the impact on existing custom code and ensure compatibility with the project's multi module structure.