You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Samuel Langlois (JIRA)" <ji...@codehaus.org> on 2014/03/19 11:49:59 UTC
[jira] (MENFORCER-189) ReactorModuleConvergence is not compatible
with 'advanced' reactor options: -pl, -rf
Samuel Langlois created MENFORCER-189:
-----------------------------------------
Summary: ReactorModuleConvergence is not compatible with 'advanced' reactor options: -pl, -rf
Key: MENFORCER-189
URL: https://jira.codehaus.org/browse/MENFORCER-189
Project: Maven Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Affects Versions: 1.4
Reporter: Samuel Langlois
I have the {{<reactorModuleConvergence/>}} rule enabled, in my multi-module build. The whole build runs fine.
However, when I use the (very handy) {{\-\-projects}} or {{\-\-resume-from}} Maven options, to limit the number of projects to build in the reactor, the rule is triggered and complains:
{code}
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.ReactorModuleConvergence failed with message:
Module parents have been found which could not be found in the reactor.
module: org.alfresco:alfresco-data-model:jar:4.3.0-BF-SNAPSHOT
{code}
This limits the interest of the rule, since we use these all the time.
Would it make sense to have a flag to disable this check, and only run the rule on projects the reactor knows?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)