<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/09/2013 12:48 PM, Stefan
Miklosovic wrote:<br>
</div>
<blockquote
cite="mid:891026099.2266264.1381337294264.JavaMail.root@redhat.com"
type="cite">
<pre wrap="">Hi,
I am getting error when generating code coverage report from aerogear-android-integration-tests.
After mvn clean install -Pemma all seems to be good but the actual genration fails with this:
<a class="moz-txt-link-freetext" href="http://pastebin.com/raw.php?i=u847VzC1">http://pastebin.com/raw.php?i=u847VzC1</a>
Manual generation of that report seems to be errorneous as well and it produces the same error ...
java -cp emma.jar emma report -r html -in coverage.em,coverage.ec
(pretty obvious since maven plugin for it does just the same thing).
1) Is here any hint how to get that generated?</pre>
</blockquote>
Not yet, but I'll take a look.<br>
<blockquote
cite="mid:891026099.2266264.1381337294264.JavaMail.root@redhat.com"
type="cite">
<pre wrap="">
2) Should not we abandon whole emma code coverage thing and stick to
something like jacoco? It is even possible to use jacoco for integration-tests repository?</pre>
</blockquote>
<br>
Emma is (last I've checked) the cc tooling that the Android SDK
supports. There may be something else, but when I put this together
a few months ago it was the only game in town.<br>
<br>
<blockquote
cite="mid:891026099.2266264.1381337294264.JavaMail.root@redhat.com"
type="cite">
<pre wrap="">
3) Are there some other tools you would like to see be used in order to escape emma?</pre>
</blockquote>
<blockquote
cite="mid:891026099.2266264.1381337294264.JavaMail.root@redhat.com"
type="cite">
<pre wrap="">
I noticed there is the dependency on emma4it-maven-plugin which has to be cloned from repository which was forked from the original one and where some changes were made. That forked repository was deleted some time ago so it does not exist anymore so I had to stick with the original one which can be the source of that error. Is there any way how we can rely on non-snapshot repos which do not get deleted randomly?
</pre>
</blockquote>
I havn't tried generating code coverage in a while so who knows.<br>
<br>
The build script is basically fondling the android build tools
underneath so it should be simple to make the modifications and host
them ourselves if it comes to it. <br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://developer.android.com/tools/testing/testing_otheride.html#AMOptionsSyntax">http://developer.android.com/tools/testing/testing_otheride.html#AMOptionsSyntax</a><br>
<br>
<blockquote
cite="mid:891026099.2266264.1381337294264.JavaMail.root@redhat.com"
type="cite">
<pre wrap="">
Stefan Miklosovic
Red Hat Brno
irc: smikloso
_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>