[
https://issues.apache.org/jira/browse/MENFORCER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Roig updated MENFORCER-231:
----------------------------------
Attachment: menforcer-231.zip
Unzip and run {{mvn validate}}
(x) The build succeeds even though child-1 points to an existing parent pom,
but with the wrong version.
(/) Next, run {{mvn -pl :child-1 validate}} and the build will fail.
> Reactor Module Convergence doesn't work when relativePath is set
> ----------------------------------------------------------------
>
> Key: MENFORCER-231
> URL: https://issues.apache.org/jira/browse/MENFORCER-231
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
> Affects Versions: 1.4
> Reporter: Daniel Roig
> Attachments: menforcer-231.zip
>
>
> When setting version to X in the root pom of a multi-module build and version
> Y in a child pom and the child pom specifies a correct {{<relativePath>}} tag
> in the parent section of the child pom, Maven will not fail the build.
> I tried invoking {{mvn validate}} from the root and it reported that the
> build succeeded. However, if I remove the {{<relativePath>}} from the parent
> section, the enforcer rule correctly reports that the module build is
> incoherent.
> Moreover, if I invoke {{mvn -pl :sub-module validate}} _with_ the
> {{<relativePath>}} reinserted, it will again correctly report an incoherent
> build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
