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.
Switch code coverage aggregation to use built-in plugin · uber/NullAway#871 | Good First Issue