-
Suggestion
-
Resolution: Won't Fix
-
None
It's always hard for us to say no to our customers. However, design decisions are not only about "Do we want to have this feature?" but also "Is this a best feature we can implement using our available resources?". We want to invest our time in making your lives (and code!) better. The fact that Google are building their Android IDE based on IntelliJ IDEA, which has a built-in coverage tool, means that you can measure code coverage for your Android apps, in an environment supported by Google. Therefore, we decided to not implement Clover for Android in the near future. Beginning of Clover 4.1 release, we will remove all documentation related to Clover for Android prototype and close the related issues.
Tasks:
- extend clover2:setup and clover2:instr adding new options for android
- integrate with android-maven-plugin (compilation, packaging, tests, ...)
- write unit tests / functional tests
- manual on CAC - general howto + clover2:setup + clover2:instr
- write code example (put in maven-clover2-plugin/src/it)
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[CLOV-570] Android for Clover-for-Maven
To do:
Android build system is now based on Gradle.
Although there are some plugins for Maven, such as:
- https://github.com/simpligility/android-maven-plugin (which seems to be maintained)
we must analyse if it's worth writing Clover integration for it.
https://spring.io/guides/gs/maven-android/
https://github.com/spring-guides/gs-maven-android -> it redirects to https://github.com/spring-guides/deprecate-gs-maven-android now;