When running "mvn verify" manually, the POM-configured excludes do work very well (hence, JaCoCo ignores those classes). When Jenkins 1.502's JaCoCo plugin processed this POM, it does *not* ignore these classes. The plugin correctly sees the POM-configured excludes... [INFO] --- jacoco-maven-plugin:0.6.2.201302030002:prepare-agent (prepare-agent) @ quipsy-inspection-roster --- [INFO] argLine set to "-javaagent:/usr/share/tomcat6/.m2/repository/org/jacoco/org.jacoco.agent/0.6.2.201302030002/org.jacoco.agent-0.6.2.201302030002-runtime.jar=destfile=/usr/share/tomcat6/.jenkins/workspace/Inspection Suite/Roster/target/jacoco.exec,excludes=*foo/bar/entities/**/*" * ...but it does not apply these... [JaCoCo plugin] exclusions: [] I can work around this problem by setting excludes in the job configuration as "**/foo/bar/entities", but I wonder if this is a bug in the plugin or if I am doing something wrong? If I need to guess: It seems the Maven JaCoCo plugin interprets "foo/bar" as "relative to target/classes" while the Jenkins JaCoCo plugin interprets the same as "relative to workspace"? Thanks! -Markus
-- 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.
