[
https://issues.apache.org/jira/browse/MCHECKSTYLE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403490#comment-16403490
]
Romain Manni-Bucau edited comment on MCHECKSTYLE-267 at 3/17/18 3:38 PM:
-------------------------------------------------------------------------
yes, I broke it with append or combine, replace works but requires to
copy/paste a lot. edit: attached parent and child pom, this one should override
just one tag. If you manage to do it with plexus then this issue is fixed - can
need some doc but not release/code :)
was (Author: romain.manni-bucau):
yes, I broke it with append or combine, replace works but requires to
copy/paste a lot.
> 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
> Attachments: pom.xml, pom.xml
>
>
> 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)
