-
Suggestion
-
Resolution: Won't Fix
-
None
Atlassian Status as of 12 October 2015
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 <clover-instr> and <clover-setup> tasks, add new options for android
- inject Clover Runtime classes into application/test JARs
- prepare sth like google's "ant emma debug" command
- prepare manuals on CAC - general "how to" + new options for clover-setup + clover-instr
- prepare code example, ship both MoneyBags and AndroidDemo in /tutorial
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
We do not plan to create integration with Ant, because currently Android toolkit is based on Gradle buld scripts and the Android Studio (based on the IntelliJ IDEA). See
CLOV-1774