[
https://issues.apache.org/jira/browse/MENFORCER-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MENFORCER-509:
-------------------------------------
Summary: ReactorModuleConvergence should better recognize multimodule roots
(was: ReactorModuleConvergence should support better recognize multimodule
roots)
> ReactorModuleConvergence should better recognize multimodule roots
> ------------------------------------------------------------------
>
> Key: MENFORCER-509
> URL: https://issues.apache.org/jira/browse/MENFORCER-509
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: reactorModuleConvergence
> Reporter: Robert Scholte
> Priority: Major
> Attachments: reactormoduleconvergence.zip
>
>
> In case there's an aggregator outside of a multimodule project to trigger one
> or more multimodules, this rule fails.
> In the code is a valid question: // After we are sure having consistent
> version we can simply use the first one?
> Most of the time the answer is yes, but not always.
> Attached is an example.
> Running {{mvn validate}} from base-project succeeds, but not from
> {{extended-project}}
> Also notice that base-project is executed before extended-project, however it
> doesn't seem to be the first of the sorted projects?!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
