However, in my development environment, the compilation environment is different.

This is not supported by JaCoCo.

Why can't you grab the class files form your server and use these class files for report generation?

Regards,
-marc


On 2017-12-19 07:15, [email protected] wrote:
when I run jacocoTestReport, I see the following error during report generation.

[ant:jacocoReport] Classes in bundle 'xxx' do no match with execution
data. For report generation the same class files must be used as at
runtime.
[ant:jacocoReport] Execution data for class xxx does not match.
[ant:jacocoReport] Execution data for class xxx does not match.
[ant:jacocoReport] Execution data for class xxx does not match.

I saw so many webpage so I know what makes this error.

-------------------------------------------------------------------
What can cause different class ids?

Class ids are identical for the exact same class file only
(byte-by-byte). There is a couple of reasons why you might get
different class files. First compiling Java source files will result
in different class files if you use a different tool chain:

Different compiler vendor (e.g. Eclipse vs. Oracle JDK)
Different compiler versions
Different compiler settings (e.g. debug vs. non-debug)
-------------------------------------------------------------------

However, in my development environment, the compilation environment is
different.
I work in Ubuntu server. can not run Ubuntu GUI mode.
so I build source code in ubuntu. but build gradle is through android
studio in windows.
and run following command in ubuntu.
./gradlew jacocoTestReport

can I receive reports properly in this environment?
how can i get report correctly?

--
You received this message because you are subscribed to the Google Groups "JaCoCo 
and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/5ef1b383935176266da9e8228cde690a%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to