> I tried that but my main point is that modules are not prevented from > scanning. >
No idea what do you mean by "scanning". If this is about SonarQube, then integration with it is not developed by us, so please refer to its documentation and support channels - see for example https://docs.sonarqube.org/latest/project-administration/narrowing-the-focus/ Also in your example no possibility > > <exclude>**/a/*.class</exclude> > <exclude>a/*.class</exclude> > <exclude>**/a/**</exclude> > Yes - you can not use module name within pattern, because patterns are relative to the module. You can place module-specific exclusions into module itself. Also different modules usually have different packages (see also Java 9 modularity and "split packages"), so that you can use package name in patterns. And for more flexibility in configuring things you can also resort to usage of JaCoCo Ant tasks via maven-ant-plugin. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/25213183-a4a2-4a3a-802d-bb3ec0e1d6d4n%40googlegroups.com.
