Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: EMMA-1.2.1
-
Fix Version/s: None
-
Component/s: Emma
-
Labels:None
-
Environment:Sonar 2.8, Android SDK r12, Win2k8, Ant 1.8, Java 1.6
-
Patch Submitted:Yes
-
Number of attachments :
Description
When analyzing an Android project, the latest upgrade of EMMA 2.0 to 2.1 breaks the ability to reuse the generated EMMA coverage reports. In fact what happens is that the build simply fails as soon as the EMMA plugin tries to load the files.
Unfortunately it's not an easy task to upgrade EMMA inside the Android SDK and therefore it would be nice to have some automatic transcoding of EMMA 2.0 files to be able to work with Android Projects again (and still have the latest plugin version in use).
As I couldn't wait for a solution to be provided, I analysed the differences between EMMA-20 and EMMA-21 file formats and created a small transcoder that I use during the ANT build (see attached files).
While this is a working solution (and maybe also a workaround for those that found this tracker case), it would really make life easier when the transcoding step could be added to the EMMA plugin.
Important Note: I'm not transcoding EMMA files in place. Instead they are copied into a temp folder first to avoid that EMMA (from Android SDK) complains about an invalid file format, the next time a build runs.
Issue Links
- is duplicated by
-
SONARPLUGINS-2146
Emma - can't use old binary format
-
Hi Juergen,
Couple of questions in order to just clarify situation :
There is no ability to use something else than Emma with Android SDK? E.g. Cobertura or JaCoCo? If so, then what's a shame. I'm asking this, because Emma is dead (latest release was 6 years ago - 2005) and so we don't want to invest a lot of time into support of a dead tool.
If I correctly understand from a code of your transcoder - there is no difference between formats 2.0 and 2.1 except of metadata, i.e. no difference in coverage data?