You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is your use-case and why do you need this feature?
At the moment, ant-calls from the org.jacoco.ant dependency are used to work with JaCoCo.
This is a less reliable way to use dependencies, because we can only check the correctness of the code in runtime, we have to use the AntBuilder mechanism that we cannot control, unwanted code is executed, and it is also difficult to add new functionality to an existing.
Describe the solution you'd like
Changes:
calling the JaCoCo code inside Gradle workers with
using classes from org.jacoco.report to work with JaCoCo, e.g. RulesChecker for verification
analyze if its API changes for different versions of JaCoCo, then we will need to create your own module for each subsequent version with an individual dependency on the corresponding version of JaCoCo
suggestion: allow users to specify their own CoverageTool heirs so that their coverage tools can be implemented
Related issues, should be fixed by this changes: #606, #544
The text was updated successfully, but these errors were encountered:
What is your use-case and why do you need this feature?
At the moment, ant-calls from the
org.jacoco.ant
dependency are used to work with JaCoCo.This is a less reliable way to use dependencies, because we can only check the correctness of the code in runtime, we have to use the AntBuilder mechanism that we cannot control, unwanted code is executed, and it is also difficult to add new functionality to an existing.
Describe the solution you'd like
Changes:
org.jacoco.report
to work with JaCoCo, e.g.RulesChecker
for verificationCoverageTool
heirs so that their coverage tools can be implementedRelated issues, should be fixed by this changes: #606, #544
The text was updated successfully, but these errors were encountered: