maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Closed] (MCOMPILER-216) Includes and excludes not passed into CompilerConfiguration
Date Fri, 16 Mar 2018 22:40:17 GMT


Michael Osipov closed MCOMPILER-216.
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> Includes and excludes not passed into CompilerConfiguration
> -----------------------------------------------------------
>                 Key: MCOMPILER-216
>                 URL:
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.1
>            Reporter: Tadeas Kriz
>            Priority: Critical
> 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:
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.

This message was sent by Atlassian JIRA

View raw message