[java code coverage] A jetty service cannot start with jacoco

jetty service start with two java processes, jetty container and application service /usr/local/java8/bin/java -jar $JETTY_HOME/start.jar -Dapp.workdir=$APP_WORK_HOME then jacoco throws java.net.BindException: Address already in use, cause both processes create agent use the same port. I found

[java code coverage] jacoco remote debug

Hi, does jacoco support the debug mode at local from the remote server? -- 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 jacoco+unsubscr...@googlegro

Re: [java code coverage] how probe array assign for runtime data

; -marc > > > On 19. Oct 2020, at 10:05, winter wrote: > > thank u for reply, which instructions do this? I found jacocoinit method > use Logger.log(Level level, String msg, Object params[]) and custom > Handler to report the boolean array, but jacocoinit was called at first

Re: [java code coverage] how probe array assign for runtime data

> > On 19. Oct 2020, at 09:30, winter wrote: > > I debug the CoreTutorial.java step by step > > final Runnable targetInstance = (Runnable) targetClass.newInstance(); > targetInstance.run(); > > when these lines were executed, it means our test target was executed, >

[java code coverage] how probe array assign for runtime data

I debug the CoreTutorial.java step by step final Runnable targetInstance = (Runnable) targetClass.newInstance(); targetInstance.run(); when these lines were executed, it means our test target was executed, then I noticed the value of probe arrays in variable store in class RuntimeData changed,

Re: [java code coverage] The exec files structure

y point in time (and already did in the past). We recommend > using the public Java API or the XML reports. > > Cheers, > -marc > > > On 22. Aug 2020, at 05:32, winter wrote: > > What's in the dump file .exec, is there some document I can study, thank u > &g

[java code coverage] The exec files structure

What's in the dump file .exec, is there some document I can study, thank u -- 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 jacoco+unsubscr...@googleg

[java code coverage] collect the coverage data by every case

I am using the jacoco on the project A, then I do some test on the project A. for example, I ran 10 test cases, I want to collect the coverage data by every case, it means I need 10 coverage data, but the 10 test cases were executed in a short time, so I cannot dump and generate report after the

Re: [java code coverage] jacoco-maven-plugin: aggregated report empty with separate aggregation and inheritance pom

Hi Marc, thanks for the clarification! On Wednesday, 13 July 2016 14:29:06 UTC+2, Marc R. Hoffmann wrote: > > Your observation about report-aggregate is also correct, see goal > documentation for details: > http://www.eclemma.org/jacoco/trunk/doc/report-aggregate-mojo.html > Yes, I read that p

Re: [java code coverage] jacoco-maven-plugin: aggregated report empty with separate aggregation and inheritance pom

As I have been fighting with that issue of an aggregate POM not being able to generate an aggregated coverage report over all listed modules exactly as Michel, I still want to make sure I understood the mechanism correctly: The goal report-aggregate does *not *work like this (when running e.g. m