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

Handle multirelease jars as input to jacoco tasks #41

Open
zml2008 opened this issue Jan 2, 2022 · 0 comments
Open

Handle multirelease jars as input to jacoco tasks #41

zml2008 opened this issue Jan 2, 2022 · 0 comments
Assignees

Comments

@zml2008
Copy link
Member

zml2008 commented Jan 2, 2022

Right now, when test coverage tasks are run jacoco doesn't know about multirelease sources, so it detects a mismatch between the executed bytecode and the source in the case of any class file using multirelease variants.

This results in error messages like:

> Task :core:jacocoTestReport
[ant:jacocoReport] Classes in bundle 'core' do not match with execution data. For report generation the same class files must be used as at runtime.
[ant:jacocoReport] Execution data for class org/spongepowered/configurate/objectmapping/RecordFieldDiscoverer$1 does not match.
[ant:jacocoReport] Execution data for class org/spongepowered/configurate/util/UnmodifiableCollections does not match.
[ant:jacocoReport] Execution data for class org/spongepowered/configurate/objectmapping/RecordFieldDiscoverer does not match.

Is it possible to resolve this, and (potentially) run coverage reports for every multirelease variant?

@zml2008 zml2008 self-assigned this Jan 2, 2022
@zml2008 zml2008 added this to the 2.2.0 milestone Feb 1, 2022
@zml2008 zml2008 removed this from the 2.2.0 milestone Sep 19, 2022
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

No branches or pull requests

1 participant