On Monday, April 8, 2019 at 7:19:55 PM UTC+2, [email protected] wrote: > > I am setting MAVEN_OPTS to include path to the jacoco agent to enable code > coverage.
MAVEN_OPTS affects JVM that runs Maven. > I see that jacoco.exec file gets generated at the end of the test run > though the exec file doesn't contain the classes that were tested in the > unit tests. I used "java -jar jacococli.jar execinfo ..." command to verify > that the classes were missing. > Now, this happens only in a remote environment (on a teamcity agent), > whereas the exec file contains the class information I expect when I run > the unit tests locally. > Wondering what could lead to this discrepancy in local versus remote > execution? Given the above statement, logically to assume that this depends on how exactly TeamCity executes Maven. Please contact TeamCity support. P.S. IMO execution of tests in the same JVM as Maven is a bad idea in general. -- 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/a4c929b1-2fb1-46a6-bc4d-5da67ad07f32%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
