[
https://issues.apache.org/jira/browse/MCHECKSTYLE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403453#comment-16403453
]
Michael Osipov commented on MCHECKSTYLE-267:
--------------------------------------------
Have you considered to alter Plexus' merge policy with
[this](https://blog.sonatype.com/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/)?
> maven merge policy breaks checkstyle inline configuration
> ---------------------------------------------------------
>
> Key: MCHECKSTYLE-267
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-267
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> This is surely a bug in maven itself since it appears in effective pom but
> please redirect and link this issue if you think so (it can be worked around
> in checkstyle plugin and I'm not sure maven cares)
> Issue is: you have a pom and a child pom. Both configure checkstyle "inline"
> (ie without checkstyle.xml but directly in <configuration>). In this case
> maven merge both configs (great) but tag by tag. it means if both checkstyle
> configs dont have the same modules then configuraiton is broken and the child
> module config can slip to another module for instance.
> Workaround would be to get raw config of both pom and do the merge in the
> plugin. Correct solution IMO is to consider attribute values during maven
> merge.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
