maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <j...@apache.org>
Subject [jira] [Closed] (MCHECKSTYLE-260) sourceDirectories property is ignored in multi-modules
Date Sat, 28 Jan 2017 01:13:25 GMT

     [ https://issues.apache.org/jira/browse/MCHECKSTYLE-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guillaume Boué closed MCHECKSTYLE-260.
--------------------------------------
       Resolution: Fixed
         Assignee: Guillaume Boué
    Fix Version/s: 3.0.0

> sourceDirectories property is ignored in multi-modules
> ------------------------------------------------------
>
>                 Key: MCHECKSTYLE-260
>                 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-260
>             Project: Maven Checkstyle Plugin
>          Issue Type: Bug
>          Components: checkstyle:check
>    Affects Versions: 2.13
>            Reporter: Andreas Dangel
>            Assignee: Guillaume Boué
>             Fix For: 3.0.0
>
>         Attachments: multi-sourcefolder-multi-modules-aggregate.zip
>
>
> I have a multi-module build which uses a plugin that generates code (xjc). The directory
is added to the compile source directories.
> With 2.13, this directory is by default scanned by checkstyle - but I want to exclude
this.
> It seems, that setting {{sourceDirectories}} doesn't have any effect for the child modules.
> Is this even the right approach to exclude a source root?
> Attached is an integration test. It just uses build-helper-maven-plugin to add an additional
source folder.
> The parent pom configures {{sourceDirectories}} to be just {{$\{project.build.sourceDirectory\}}}.
I would have expected, that checkstyle doesn't find any violations, as {{src/generated/java}}
shouldn't be checked.
> I think, it's related with the change MCHECKSTYLE-70.
> It works with 2.12



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message