Unfortunately, the problem have not fixed yet. See the issue https://github.com/jacoco/jacoco/issues/67 for more details.
Regards, Kioncopxki On Wednesday, July 24, 2013 8:57:34 AM UTC+7, Niranjan Rao wrote: > > For my deployment, I have one master pom which includes bunch of other > modules. Basically standard setup which, works from maven command line > just fine. > > I have setup jenkins to record JaCoCo coverage report. Problem is one > the pom file is just a placeholder maven project which does not have any > source associated with it. Its used for deploying multiple web > applications in one shot. Reasoning is my deployment settings are only > at one location. This pom declares dependency on other web applications > and uses maven cargo plugin to deploy many war files. > > When I run this in hudson, JaCoco plugin complains about missing classes > directory. > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.jacoco:jacoco-maven-plugin:0.6.1.201212231917:report > (post-unit-test) on project qaDeployer: Execution post-unit-test of goal > org.jacoco:jacoco-maven-plugin:0.6.1.201212231917:report failed: basedir > /var/lib/jenkins/jobs/Snapshot_build/workspace/qaDeployer/target/classes > does not exist > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) > > > > What do I need to do so that this module is excluded from JaCoCo > settings. I have tried settings exclusion pattern as **/qaDeployer/**/* > but it does not help. > > Regards, > > Niranjan > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
