[JIRA] [jacoco] (JENKINS-21658) Provide option to exclude complete Maven modules from JaCoCo report

Mon, 10 Mar 2014 01:43:29 -0700

I have the same problem. The includes/excludes appear to be evaluated relative to the class directory. It is onerous and brittle to add specific exclusions on a package by package basis.

IMHO, rather than an option to exclude specific maven modules, the plugin should ignore un-instrumented class files.

This would address the problem without being maven specific. In the maven configuration, modules could then be excluded by configuring them to skip jacoco instrumentation...

<plugin>
    <groupId>org.jacoco</groupId>
    <artifactId>jacoco-maven-plugin</artifactId>
    <configuration>
        <skip>true</skip>
    </configuration>
</plugin>


... and code within modules to be excluded by configuring the agent to be more selective ...





<plugin>
    <groupId>org.jacoco</groupId>
    <artifactId>jacoco-maven-plugin</artifactId>
    <version>${jacoco-plugin.version}</version>
    <executions>
        <execution>
            <goals>
                <goal>prepare-agent</goal>
            </goals>
            <configuration>
                <includes>
                    <include>com.foo.*</include>
                </includes>
            </configuration>
        </execution>
    </executions>
</plugin>
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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/d/optout.

Reply via email to