Sources must be in sub-directories of the Jenkins job's workspace. For jobs using a custom workspace this will typically not be the case.
Classes must be present as loose class files in sub-directories of the Jenkins job's workspace. It should be possible to specify a generalized class path involving arbitrary directories and JAR files.
Inclusions and exclusions must be specified as a class file filter pattern. This is counter-intuitive and also contrary to the wildcard package/class matching pattern supported by the JaCoCo agent.
[JENKINS-19621] Plug-in configuration is inflexible and counter-intuitive
Bug
Major
