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

KSP issue on KMM/KMP project for jacocoAggregatedReport task #197

Closed
ArcherEmiya05 opened this issue Nov 26, 2024 · 1 comment
Closed

KSP issue on KMM/KMP project for jacocoAggregatedReport task #197

ArcherEmiya05 opened this issue Nov 26, 2024 · 1 comment

Comments

@ArcherEmiya05
Copy link

ArcherEmiya05 commented Nov 26, 2024

With the latest version 2.3.x, the aggregation of unit test results now includes JVM and works fine. However aggregation for code coverage report fails.

* What went wrong:
Some problems were found with the configuration of task ':Kommon:allVariantsSourcesForCoverageReport' (type 'Sync').
  - Gradle detected a problem with the following location: '/Users/jensenlouiselim/Desktop/Projects/Mobile/KMM/Cryptonian/Kommon/build/generated/ksp/jvm/jvmMain/kotlin'.
    
    Reason: Task ':Kommon:allVariantsSourcesForCoverageReport' uses this output of task ':Kommon:kspKotlinJvm' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':Kommon:kspKotlinJvm' as an input of ':Kommon:allVariantsSourcesForCoverageReport'.
      2. Declare an explicit dependency on ':Kommon:kspKotlinJvm' from ':Kommon:allVariantsSourcesForCoverageReport' using Task#dependsOn.
      3. Declare an explicit dependency on ':Kommon:kspKotlinJvm' from ':Kommon:allVariantsSourcesForCoverageReport' using Task#mustRunAfter.
    
    For more information, please refer to https://docs.gradle.org/8.9/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.

Already report this issue on KSP repo but I feel like this issue must be check here as well. Maybe an update to README.md if this is a configuration issue?

@gmazzo
Copy link
Owner

gmazzo commented Nov 26, 2024

Fixed at 2.3.1!

@gmazzo gmazzo closed this as completed Nov 26, 2024
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

2 participants