Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Auto Closed
-
3.1
-
None
-
None
Description
When <includes>, <exclusions>, <testIncludes> or <testExcludes> are set in the configuration of maven-compiler-plugin in the pom.xml file, it doesn't propagate into the used compiler as part of the CompilerConfiguration, although the CompilerConfiguration has getters and setters for includes and excludes.
There's an example:
groovy-eclipse-compiler is built on top of plexus-compiler API and as you can see here: https://github.com/groovy/groovy-eclipse/blob/master/extras/groovy-eclipse-compiler/src/main/java/org/codehaus/groovy/eclipse/compiler/GroovyEclipseCompiler.java#L150 they use the getIncludes() and getExcludes() from the CompilerConfiguration, so plugin users can decide what will be included or excluded. Unfortunately, the getIncludes() and getExcludes() always return empty Set.
In our scenario, we wanted to exclude all .java files, but because of this bug, there is no such way to do this, even though there should be.