You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@apache.org> on 2017/06/22 20:36:00 UTC
[jira] [Updated] (MENFORCER-231) Reactor Module Convergence doesn't
work when relativePath is set
[ https://issues.apache.org/jira/browse/MENFORCER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MENFORCER-231:
---------------------------------------
Fix Version/s: (was: 3.0.0)
3.0.1
> 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
> Fix For: 3.0.1
>
> 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.4.14#64029)