[java code coverage] Skipping JaCoCo execution due to missing execution data file

[tusharkapadnis2013]

Hi Team,

I have been trying to integrate the jacoco with my project for code 
coverage but I am getting "Skipping JaCoCo execution due to missing 
execution data file" message.

I have tried many things but it did not work. Could you please me on this?. 
My pom.xml configuration given below.



org.jacoco

jacoco-maven-plugin

0.8.5





pre-unit-test



prepare-agent







${project.build.directory}/coverage-reports/jacoco-ut.exec

surefireArgLine 









post-unit-test

test



report





${project.build.directory}/coverage-reports/jacoco-ut.exec

${project.reporting.outputDirectory}/jacoco-ut











 

org.apache.maven.plugins

maven-surefire-plugin

3.0.0-M4



${surefireArgLine}






I tried removing argLine in maven-surefire but I can see "*The forked VM 
terminated without properly saying goodbye. VM crash or System.exit called?*
"


I tried removing  from Jacoco but still, it didn't work. 


I tried  as 0 in Surefire but no luck. Even tried  
-Xmx1024m 
-XX:MaxPermSize=256m and 
false but none of this worked.



Please let me know if you have any suggestions.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/89ad93e9-43c0-441d-9aab-dbff9bc6f1c4%40googlegroups.com.

Re: [java code coverage] Skipping JaCoCo execution due to missing execution data file

[Joel Costigliola]

Thanks Evgeny for the help! We will use @{argLine}  as
you suggested.

Cheers

On Wed, Dec 4, 2019 at 12:05 AM Evgeny Mandrikov 
wrote:

>
>
>
>> On Sun, Dec 1, 2019 at 7:17 PM  wrote:
>>
>>> I'm the lead developer of AssertJ Core and I could use a bit of help
>>> trying to identify why jacoco is missing the execution data file.
>>> It is likely something misconfigured but I can't put my finger on it.
>>>
>>
> Hi Joel,
>
> You have following configuration of maven-surefire-plugin (
> https://github.com/joel-costigliola/assertj-core/blob/e5bdf79013895ffa3f94b090d4598912c4fccd42/pom.xml#L230-L235
>  )
>
> 
>   maven-surefire-plugin
>   
> ${argLine}
>   
> 
>
> whereas according to documentation of jacoco-maven-plugin goal
> prepare-agent (
> https://www.jacoco.org/jacoco/trunk/doc/prepare-agent-mojo.html )
> either argLine should be specified only as a property and not in
> configuration,
> or syntax for late property evaluation (
> http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#late-property-evaluation
>  )
> should be used.
>
> Removal of argLine from configuration won't work, because it is also
> specified in parent pom (
> https://github.com/joel-costigliola/assertj-maven-parent-pom/blob/assertj-parent-pom-2.2.6/pom.xml#L376
> ) and therefore will be inherited - you can check this using
> help:effective-pom
>
> According to my experiments for your project, use of late property
> evaluation works perfectly:
>
> 
>   maven-surefire-plugin
>   
> @{argLine}
>   
> 
>
>
>
> BTW nice to see that AssertJ uses JaCoCo! I added it to page
> https://github.com/jacoco/jacoco/wiki/Projects-that-use-JaCoCo
>
>
> Regards,
> Evgeny
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "JaCoCo and EclEmma Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jacoco/8eQQzVXMIjs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jacoco+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jacoco/34ad9c42-f21c-4134-a839-9bad42908111%40googlegroups.com
> 
> .
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/CAC0j%3DP1nn8VXdhDP9xvHgHO%2BsAQOv%3DFeCiVHhN5_dk7Ak%2BjaVA%40mail.gmail.com.

Re: [java code coverage] Skipping JaCoCo execution due to missing execution data file

[Evgeny Mandrikov]

 

> On Sun, Dec 1, 2019 at 7:17 PM  wrote:
>
>> I'm the lead developer of AssertJ Core and I could use a bit of help 
>> trying to identify why jacoco is missing the execution data file.
>> It is likely something misconfigured but I can't put my finger on it.
>>
>
Hi Joel,

You have following configuration of maven-surefire-plugin ( 
https://github.com/joel-costigliola/assertj-core/blob/e5bdf79013895ffa3f94b090d4598912c4fccd42/pom.xml#L230-L235
 )


  maven-surefire-plugin
  
${argLine}
  


whereas according to documentation of jacoco-maven-plugin goal 
prepare-agent ( 
https://www.jacoco.org/jacoco/trunk/doc/prepare-agent-mojo.html )
either argLine should be specified only as a property and not in 
configuration,
or syntax for late property evaluation ( 
http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#late-property-evaluation
 ) 
should be used.

Removal of argLine from configuration won't work, because it is also 
specified in parent pom ( 
https://github.com/joel-costigliola/assertj-maven-parent-pom/blob/assertj-parent-pom-2.2.6/pom.xml#L376
 
) and therefore will be inherited - you can check this using 
help:effective-pom

According to my experiments for your project, use of late property 
evaluation works perfectly:


  maven-surefire-plugin
  
@{argLine}
  




BTW nice to see that AssertJ uses JaCoCo! I added it to page 
https://github.com/jacoco/jacoco/wiki/Projects-that-use-JaCoCo


Regards,
Evgeny

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/34ad9c42-f21c-4134-a839-9bad42908111%40googlegroups.com.

Re: [java code coverage] Skipping JaCoCo execution due to missing execution data file

[Joel Costigliola]

we found a workaround by removing the argLine settings in the java 9 maven
profile, we are still not sure why this overrding the jacoco arg.

since assertj-core development continues, I have created a *jacoco* branch
to reproduce the issue (don't use master branch anymore).

On Sun, Dec 1, 2019 at 7:17 PM  wrote:

> Hi,
>
> I'm the lead developer of AssertJ Core and I could use a bit of help
> trying to identify why jacoco is missing the execution data file.
> It is likely something misconfigured but I can't put my finger on it.
>
> You should be able to reproduce the issue by cloning
> https://github.com/joel-costigliola/assertj-core and executing
>
> mvn clean jacoco:prepare-agent package jacoco:report
> -Dtest=StandardRepresentation_toStringOf_Test
>
> (you can execute all the tests but there are more than 1000 so executing
> just one is way quicker).
>
> I have verified that I was surefire plugin was configured with forkCount =
> 1 (so not 0).
> The build run jacoco prepare-agent which outputs
>
> [INFO] argLine set to
> -javaagent:/home/joel/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/joel/prog/assertj/assertj-core-3.x/target/jacoco.exec,excludes=**/*hamcrest*/**
> --add-opens java.base/java.lang=ALL-UNNAMED --add-opens
> java.base/java.util=ALL-UNNAMED
>  --add-opens
>  java.base/java.io=ALL-UNNAMED --add-opens java.base/java.math=ALL-UNNAMED
>
> I have executed the build in debug and found that surefire argline did not
> show jacoco destfile setting, I'm not sure if that's a problem ...
>
> argLine = --add-opens java.base/java.lang=ALL-UNNAMED --add-opens
> java.base/java.util=ALL-UNNAMED
>   --add-opens
>   java.base/java.io=ALL-UNNAMED --add-opens
> java.base/java.math=ALL-UNNAMED
>
>
> My environment looks like:
>
> Maven home: /home/joel/prog/apache-maven-3.5.3
> Java version: 11.0.2, vendor: Oracle Corporation
> Java home: /home/joel/.sdkman/candidates/java/11.0.2-open
> Default locale: en_NZ, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-169-generic", arch: "amd64", family:
> "unix"
>
>
> Any help  would be welcome as I'm running out of ideas.
>
> Cheers
>
> Joel Costigliola
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "JaCoCo and EclEmma Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jacoco/8eQQzVXMIjs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jacoco+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jacoco/48ec4077-1931-4227-959f-1effd6e72d14%40googlegroups.com
> 
> .
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/CAC0j%3DP1%3Dame36GJrhZZrGhd_PqnCk3KFFuYVZL5czyGajM_GDA%40mail.gmail.com.

[java code coverage] Skipping JaCoCo execution due to missing execution data file

[joel . costigliola]

Hi,

I'm the lead developer of AssertJ Core and I could use a bit of help trying 
to identify why jacoco is missing the execution data file.
It is likely something misconfigured but I can't put my finger on it.

You should be able to reproduce the issue by cloning 
https://github.com/joel-costigliola/assertj-core and executing

mvn clean jacoco:prepare-agent package jacoco:report 
-Dtest=StandardRepresentation_toStringOf_Test

(you can execute all the tests but there are more than 1000 so executing 
just one is way quicker).

I have verified that I was surefire plugin was configured with forkCount = 
1 (so not 0).
The build run jacoco prepare-agent which outputs

[INFO] argLine set to 
-javaagent:/home/joel/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/joel/prog/assertj/assertj-core-3.x/target/jacoco.exec,excludes=**/*hamcrest*/**
 
--add-opens java.base/java.lang=ALL-UNNAMED --add-opens 
java.base/java.util=ALL-UNNAMED
 --add-opens
 java.base/java.io=ALL-UNNAMED --add-opens java.base/java.math=ALL-UNNAMED

I have executed the build in debug and found that surefire argline did not 
show jacoco destfile setting, I'm not sure if that's a problem ... 

argLine = --add-opens java.base/java.lang=ALL-UNNAMED --add-opens 
java.base/java.util=ALL-UNNAMED
  --add-opens
  java.base/java.io=ALL-UNNAMED --add-opens 
java.base/java.math=ALL-UNNAMED


My environment looks like:

Maven home: /home/joel/prog/apache-maven-3.5.3
Java version: 11.0.2, vendor: Oracle Corporation
Java home: /home/joel/.sdkman/candidates/java/11.0.2-open
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-169-generic", arch: "amd64", family: 
"unix"


Any help  would be welcome as I'm running out of ideas.

Cheers

Joel Costigliola

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/48ec4077-1931-4227-959f-1effd6e72d14%40googlegroups.com.

[java code coverage] Skipping JaCoCo execution due to missing execution data file.

[bharuka . rupesh]

Hi,
I am getting "Skipping JaCoCo execution due to missing execution data file" 
message and Jacoco test report is not generated.

You can have a look on below pom.xml configuration. Can you please help me in 
identifying the root cause of the problem?



  jacoco
 reuseReports
 target/jacoco.exec
 java





maven-surefire-plugin
2.22.0

1
true
${jacoco.agent.argLine}



org.ow2.asm
asm
6.2




org.jacoco
jacoco-maven-plugin
0.8.1
 
 true
 
 

jacoco-initialize
initialize

prepare-agent


   jacoco.agent.argLine
   target/jacoco.exec  
  



 jacoco-report
 verify
 
report
  

  



-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/40ed37e9-d5c3-4317-855a-f8780d97d9e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [java code coverage] "Skipping JaCoCo execution due to missing execution data file." only in CI environment

[pilch . patrick . s]

Evgeny,

Adding a MAVEN_SKIP_RC 'env' entry in my .travis.yml did the trick!

Thanks Evgeny & Mirko

On Tuesday, July 5, 2016 at 2:28:36 AM UTC-5, Evgeny Mandrikov wrote:
> Hi Patrick,
> 
> 
> I think that the problem in Travis is that configuration done by 
> maven-invoker-plugin via mavenOpts is overwritten by "~/.mavenrc", which is 
> presented in Travis. We faced the same issue in the build of JaCoCo itself - 
> see our description and solution at 
> https://github.com/jacoco/jacoco/blob/master/.travis.sh#L59
> 
> On Tuesday, July 5, 2016 at 6:59:33 AM UTC+2, Mirko Friedenhagen wrote:
> Hello,
> 
> the prepare steps only set a system property argLine, which is picked up by 
> surefire resp. failsafe plugins and added for the forked test JVM. You are 
> using the invoker plugin, where an equivalent option is called invokerOpts, 
> see http://maven.apache.org/plugins/maven-invoker-plugin/run-mojo.html.
> 
> Try setting a property ${argLine}.
> 
> Regards
> 
> Mirko
> 
> -- 
> 
> Sent from my mobile
> 
> Am 05.07.2016 00:38 schrieb  :
> Hi Mirko,
> 
> 
> 
> Unfortunately that did not solve the issue.
> 
> 
> 
> Commands executed:
> 
> mvn -N io.takari:maven:wrapper -Dmaven=3.3.9
> 
> ./mvnw --show-version clean verify
> 
> 
> 
> Output here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/fac1d3372bb24d18f3df7fcba5a8acc9a0c4296a/wrapper_test.txt
> 
> 
> 
> 
> On Monday, July 4, 2016 at 4:36:02 PM UTC-5, Mirko Friedenhagen wrote:
> 
> > Hello,
> 
> >
> 
> > you could try to use Maven 3.3.9 as well in Travis, see
> 
> >
> 
> > https://github.com/mojohaus/mojo-parent/blob/master/.travis.yml for how to 
> > use the takari wrapper plugin.
> 
> >
> 
> > Regards
> 
> >
> 
> > Mirko
> 
> >
> 
> > --
> 
> >
> 
> > Sent from my mobile
> 
> >
> 
> 
> > Am 04.07.2016 22:15 schrieb  :
> 
> > Hello,
> 
> >
> 
> >
> 
> >
> 
> > I am trying to debug an issue I'm experiencing with JaCoCo that manifests 
> > in my CI environment (Travis), but not locally on my workstation. My 
> > intended goal is to have two separate reports produced by JaCoCo - one for 
> > unit tests, and the other for integration tests.
> 
> >
> 
> >
> 
> >
> 
> > On my workstation running Maven 3.3.9 and JDK 1.8.0_91, everything works as 
> > intended when I run standard lifecycle goals like "install" or "verify". I 
> > based my configuration off of 
> > https://github.com/Godin/sonar-experiments/blob/master/jacoco-examples/maven-invoker-plugin-example/pom.xml
> 
> >
> 
> > My ${project.reporting.outputDirectory} successfully contains "jacoco-it" 
> > and "jacoco-ut".
> 
> >
> 
> > My POM file is here: 
> > https://github.com/patrickpilch/dependency-license-checker/blob/d4a3e3370639c2f52d7083ca5163cdaaace3ba15/pom.xml#L153
> >  and a debug log of a successful local build is here: 
> > https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/local_build_log.md
> 
> >
> 
> >
> 
> >
> 
> > The problem I'm experiencing is that when trying to build in my CI 
> > environment, only the JaCoCo unit tests .exec file and reports appear. The 
> > Travis build debug output with environment details and versions is here: 
> > https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/ci_build_output.md
> 
> >
> 
> >
> 
> >
> 
> > It's easy to reproduce this on a Travis docker container. Instructions 
> > here: 
> > https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/steps_to_reproduce.md
> 
> >
> 
> >
> 
> >
> 
> > Any help would be appreciated. Thank you!
> 
> >
> 
> >
> 
> >
> 
> > --
> 
> >
> 
> > 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+un...@googlegroups.com.
> 
> 
> >
> 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/jacoco/0ebc42d3-0228-4ab5-a4a8-d6e54050a554%40googlegroups.com.
> 
> >
> 
> > For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> --
> 
> 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+un...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jacoco/952a70a2-8f42-4b3b-b563-acfc278319c6%40googlegroups.com.
> 
> 
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.go

Re: [java code coverage] "Skipping JaCoCo execution due to missing execution data file." only in CI environment

[Evgeny Mandrikov]

Hi Patrick,

I think that the problem in Travis is that configuration done by 
maven-invoker-plugin via mavenOpts is overwritten by "~/.mavenrc", which is 
presented in Travis. We faced the same issue in the build of JaCoCo itself 
- see our description and solution at 
https://github.com/jacoco/jacoco/blob/master/.travis.sh#L59

On Tuesday, July 5, 2016 at 6:59:33 AM UTC+2, Mirko Friedenhagen wrote:
>
> Hello,
>
> the prepare steps only set a system property argLine, which is picked up 
> by surefire resp. failsafe plugins and added for the forked test JVM. You 
> are using the invoker plugin, where an equivalent option is called 
> invokerOpts, see 
> http://maven.apache.org/plugins/maven-invoker-plugin/run-mojo.html.
>
> Try setting a property ${argLine}.
>
> Regards
> Mirko
> -- 
> Sent from my mobile
> Am 05.07.2016 00:38 schrieb :
>
> Hi Mirko,
>
> Unfortunately that did not solve the issue.
>
> Commands executed:
> mvn -N io.takari:maven:wrapper -Dmaven=3.3.9
> ./mvnw --show-version clean verify
>
> Output here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/fac1d3372bb24d18f3df7fcba5a8acc9a0c4296a/wrapper_test.txt
>
> On Monday, July 4, 2016 at 4:36:02 PM UTC-5, Mirko Friedenhagen wrote:
> > Hello,
> >
> > you could try to use Maven 3.3.9 as well in Travis, see
> >
> > https://github.com/mojohaus/mojo-parent/blob/master/.travis.yml for how 
> to use the takari wrapper plugin.
> >
> > Regards
> >
> > Mirko
> >
> > --
> >
> > Sent from my mobile
> >
> > Am 04.07.2016 22:15 schrieb  :
> > Hello,
> >
> >
> >
> > I am trying to debug an issue I'm experiencing with JaCoCo that 
> manifests in my CI environment (Travis), but not locally on my workstation. 
> My intended goal is to have two separate reports produced by JaCoCo - one 
> for unit tests, and the other for integration tests.
> >
> >
> >
> > On my workstation running Maven 3.3.9 and JDK 1.8.0_91, everything works 
> as intended when I run standard lifecycle goals like "install" or "verify". 
> I based my configuration off of 
> https://github.com/Godin/sonar-experiments/blob/master/jacoco-examples/maven-invoker-plugin-example/pom.xml
> >
> > My ${project.reporting.outputDirectory} successfully contains 
> "jacoco-it" and "jacoco-ut".
> >
> > My POM file is here: 
> https://github.com/patrickpilch/dependency-license-checker/blob/d4a3e3370639c2f52d7083ca5163cdaaace3ba15/pom.xml#L153
>  
> and a debug log of a successful local build is here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/local_build_log.md
> >
> >
> >
> > The problem I'm experiencing is that when trying to build in my CI 
> environment, only the JaCoCo unit tests .exec file and reports appear. The 
> Travis build debug output with environment details and versions is here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/ci_build_output.md
> >
> >
> >
> > It's easy to reproduce this on a Travis docker container. Instructions 
> here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/steps_to_reproduce.md
> >
> >
> >
> > Any help would be appreciated. Thank you!
> >
> >
> >
> > --
> >
> > 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+un...@googlegroups.com.
> >
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jacoco/0ebc42d3-0228-4ab5-a4a8-d6e54050a554%40googlegroups.com
> .
> >
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jacoco/952a70a2-8f42-4b3b-b563-acfc278319c6%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/766290da-ee62-4d5c-8c43-16d495b5edaa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [java code coverage] "Skipping JaCoCo execution due to missing execution data file." only in CI environment

[Mirko Friedenhagen]

Hello,

the prepare steps only set a system property argLine, which is picked up by
surefire resp. failsafe plugins and added for the forked test JVM. You are
using the invoker plugin, where an equivalent option is called invokerOpts,
see http://maven.apache.org/plugins/maven-invoker-plugin/run-mojo.html.

Try setting a property ${argLine}.

Regards
Mirko
-- 
Sent from my mobile
Am 05.07.2016 00:38 schrieb :

Hi Mirko,

Unfortunately that did not solve the issue.

Commands executed:
mvn -N io.takari:maven:wrapper -Dmaven=3.3.9
./mvnw --show-version clean verify

Output here:
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/fac1d3372bb24d18f3df7fcba5a8acc9a0c4296a/wrapper_test.txt

On Monday, July 4, 2016 at 4:36:02 PM UTC-5, Mirko Friedenhagen wrote:
> Hello,
>
> you could try to use Maven 3.3.9 as well in Travis, see
>
> https://github.com/mojohaus/mojo-parent/blob/master/.travis.yml for how
to use the takari wrapper plugin.
>
> Regards
>
> Mirko
>
> --
>
> Sent from my mobile
>
> Am 04.07.2016 22:15 schrieb  :
> Hello,
>
>
>
> I am trying to debug an issue I'm experiencing with JaCoCo that manifests
in my CI environment (Travis), but not locally on my workstation. My
intended goal is to have two separate reports produced by JaCoCo - one for
unit tests, and the other for integration tests.
>
>
>
> On my workstation running Maven 3.3.9 and JDK 1.8.0_91, everything works
as intended when I run standard lifecycle goals like "install" or "verify".
I based my configuration off of
https://github.com/Godin/sonar-experiments/blob/master/jacoco-examples/maven-invoker-plugin-example/pom.xml
>
> My ${project.reporting.outputDirectory} successfully contains "jacoco-it"
and "jacoco-ut".
>
> My POM file is here:
https://github.com/patrickpilch/dependency-license-checker/blob/d4a3e3370639c2f52d7083ca5163cdaaace3ba15/pom.xml#L153
and a debug log of a successful local build is here:
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/local_build_log.md
>
>
>
> The problem I'm experiencing is that when trying to build in my CI
environment, only the JaCoCo unit tests .exec file and reports appear. The
Travis build debug output with environment details and versions is here:
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/ci_build_output.md
>
>
>
> It's easy to reproduce this on a Travis docker container. Instructions
here:
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/steps_to_reproduce.md
>
>
>
> Any help would be appreciated. Thank you!
>
>
>
> --
>
> 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+un...@googlegroups.com.
>
> To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/0ebc42d3-0228-4ab5-a4a8-d6e54050a554%40googlegroups.com
.
>
> For more options, visit https://groups.google.com/d/optout.

--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/952a70a2-8f42-4b3b-b563-acfc278319c6%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/CAK8jvqzGNxt-QR92E6ZLKwSJU1xY6f05qMAn-sNFjq%2BD%3DxQDVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [java code coverage] "Skipping JaCoCo execution due to missing execution data file." only in CI environment

[pilch . patrick . s]

Hi Mirko,

Unfortunately that did not resolve the issue.

Commands executed:
mvn -N io.takari:maven:wrapper -Dmaven=3.3.9
./mvnw --show-version clean verify

Output here: 
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/fac1d3372bb24d18f3df7fcba5a8acc9a0c4296a/wrapper_test.txt

On Monday, July 4, 2016 at 4:36:02 PM UTC-5, Mirko Friedenhagen wrote:
> Hello,
> 
> you could try to use Maven 3.3.9 as well in Travis, see 
> 
> https://github.com/mojohaus/mojo-parent/blob/master/.travis.yml for how to 
> use the takari wrapper plugin.
> 
> Regards
> 
> Mirko
> 
> -- 
> 
> Sent from my mobile
> 
> Am 04.07.2016 22:15 schrieb  :
> Hello,
> 
> 
> 
> I am trying to debug an issue I'm experiencing with JaCoCo that manifests in 
> my CI environment (Travis), but not locally on my workstation. My intended 
> goal is to have two separate reports produced by JaCoCo - one for unit tests, 
> and the other for integration tests.
> 
> 
> 
> On my workstation running Maven 3.3.9 and JDK 1.8.0_91, everything works as 
> intended when I run standard lifecycle goals like "install" or "verify". I 
> based my configuration off of 
> https://github.com/Godin/sonar-experiments/blob/master/jacoco-examples/maven-invoker-plugin-example/pom.xml
> 
> My ${project.reporting.outputDirectory} successfully contains "jacoco-it" and 
> "jacoco-ut".
> 
> My POM file is here: 
> https://github.com/patrickpilch/dependency-license-checker/blob/d4a3e3370639c2f52d7083ca5163cdaaace3ba15/pom.xml#L153
>  and a debug log of a successful local build is here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/local_build_log.md
> 
> 
> 
> The problem I'm experiencing is that when trying to build in my CI 
> environment, only the JaCoCo unit tests .exec file and reports appear. The 
> Travis build debug output with environment details and versions is here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/ci_build_output.md
> 
> 
> 
> It's easy to reproduce this on a Travis docker container. Instructions here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/steps_to_reproduce.md
> 
> 
> 
> Any help would be appreciated. Thank you!
> 
> 
> 
> --
> 
> 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+un...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jacoco/0ebc42d3-0228-4ab5-a4a8-d6e54050a554%40googlegroups.com.
> 
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/74283200-d468-4ca7-9775-81ae4e89c302%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [java code coverage] "Skipping JaCoCo execution due to missing execution data file." only in CI environment

[teunic0rn]

Hi Mirko,

Unfortunately that did not solve the issue.

Commands executed:
mvn -N io.takari:maven:wrapper -Dmaven=3.3.9
./mvnw --show-version clean verify

Output here: 
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/fac1d3372bb24d18f3df7fcba5a8acc9a0c4296a/wrapper_test.txt

On Monday, July 4, 2016 at 4:36:02 PM UTC-5, Mirko Friedenhagen wrote:
> Hello,
> 
> you could try to use Maven 3.3.9 as well in Travis, see 
> 
> https://github.com/mojohaus/mojo-parent/blob/master/.travis.yml for how to 
> use the takari wrapper plugin.
> 
> Regards
> 
> Mirko
> 
> -- 
> 
> Sent from my mobile
> 
> Am 04.07.2016 22:15 schrieb  :
> Hello,
> 
> 
> 
> I am trying to debug an issue I'm experiencing with JaCoCo that manifests in 
> my CI environment (Travis), but not locally on my workstation. My intended 
> goal is to have two separate reports produced by JaCoCo - one for unit tests, 
> and the other for integration tests.
> 
> 
> 
> On my workstation running Maven 3.3.9 and JDK 1.8.0_91, everything works as 
> intended when I run standard lifecycle goals like "install" or "verify". I 
> based my configuration off of 
> https://github.com/Godin/sonar-experiments/blob/master/jacoco-examples/maven-invoker-plugin-example/pom.xml
> 
> My ${project.reporting.outputDirectory} successfully contains "jacoco-it" and 
> "jacoco-ut".
> 
> My POM file is here: 
> https://github.com/patrickpilch/dependency-license-checker/blob/d4a3e3370639c2f52d7083ca5163cdaaace3ba15/pom.xml#L153
>  and a debug log of a successful local build is here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/local_build_log.md
> 
> 
> 
> The problem I'm experiencing is that when trying to build in my CI 
> environment, only the JaCoCo unit tests .exec file and reports appear. The 
> Travis build debug output with environment details and versions is here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/ci_build_output.md
> 
> 
> 
> It's easy to reproduce this on a Travis docker container. Instructions here: 
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/steps_to_reproduce.md
> 
> 
> 
> Any help would be appreciated. Thank you!
> 
> 
> 
> --
> 
> 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+un...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jacoco/0ebc42d3-0228-4ab5-a4a8-d6e54050a554%40googlegroups.com.
> 
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/952a70a2-8f42-4b3b-b563-acfc278319c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [java code coverage] "Skipping JaCoCo execution due to missing execution data file." only in CI environment

[Mirko Friedenhagen]

Hello,

you could try to use Maven 3.3.9 as well in Travis, see
https://github.com/mojohaus/mojo-parent/blob/master/.travis.yml for how to
use the takari wrapper plugin.

Regards
Mirko
-- 
Sent from my mobile
Am 04.07.2016 22:15 schrieb :

> Hello,
>
> I am trying to debug an issue I'm experiencing with JaCoCo that manifests
> in my CI environment (Travis), but not locally on my workstation. My
> intended goal is to have two separate reports produced by JaCoCo - one for
> unit tests, and the other for integration tests.
>
> On my workstation running Maven 3.3.9 and JDK 1.8.0_91, everything works
> as intended when I run standard lifecycle goals like "install" or "verify".
> I based my configuration off of
> https://github.com/Godin/sonar-experiments/blob/master/jacoco-examples/maven-invoker-plugin-example/pom.xml
> My ${project.reporting.outputDirectory} successfully contains "jacoco-it"
> and "jacoco-ut".
> My POM file is here:
> https://github.com/patrickpilch/dependency-license-checker/blob/d4a3e3370639c2f52d7083ca5163cdaaace3ba15/pom.xml#L153
> and a debug log of a successful local build is here:
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/local_build_log.md
>
> The problem I'm experiencing is that when trying to build in my CI
> environment, only the JaCoCo unit tests .exec file and reports appear. The
> Travis build debug output with environment details and versions is here:
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/ci_build_output.md
>
> It's easy to reproduce this on a Travis docker container. Instructions
> here:
> https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/steps_to_reproduce.md
>
> Any help would be appreciated. Thank you!
>
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jacoco/0ebc42d3-0228-4ab5-a4a8-d6e54050a554%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/CAK8jvqzD%2BQ%2BH3a7sKhaeDLOTYDDzAM4%3DCUrwhCHhsLKiyDkhbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[java code coverage] "Skipping JaCoCo execution due to missing execution data file." only in CI environment

[pilch . patrick . s]

Hello,

I am trying to debug an issue I'm experiencing with JaCoCo that manifests in my 
CI environment (Travis), but not locally on my workstation. My intended goal is 
to have two separate reports produced by JaCoCo - one for unit tests, and the 
other for integration tests.

On my workstation running Maven 3.3.9 and JDK 1.8.0_91, everything works as 
intended when I run standard lifecycle goals like "install" or "verify". I 
based my configuration off of 
https://github.com/Godin/sonar-experiments/blob/master/jacoco-examples/maven-invoker-plugin-example/pom.xml
My ${project.reporting.outputDirectory} successfully contains "jacoco-it" and 
"jacoco-ut".
My POM file is here: 
https://github.com/patrickpilch/dependency-license-checker/blob/d4a3e3370639c2f52d7083ca5163cdaaace3ba15/pom.xml#L153
 and a debug log of a successful local build is here: 
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/local_build_log.md

The problem I'm experiencing is that when trying to build in my CI environment, 
only the JaCoCo unit tests .exec file and reports appear. The Travis build 
debug output with environment details and versions is here: 
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/ci_build_output.md

It's easy to reproduce this on a Travis docker container. Instructions here: 
https://gist.githubusercontent.com/patrickpilch/21d32e367b312443c98cbf2bcaa687fa/raw/c0784a269d744e165ab5cdf533c87e01c668/steps_to_reproduce.md

Any help would be appreciated. Thank you!

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/0ebc42d3-0228-4ab5-a4a8-d6e54050a554%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.