[
https://issues.apache.org/jira/browse/MENFORCER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151643#comment-17151643
]
Robert Scholte commented on MENFORCER-304:
------------------------------------------
Fixed in
[1d47fd94eca04a804abf3b86364904c5b852ea61|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commit;h=1d47fd94eca04a804abf3b86364904c5b852ea61]
> Improve dependency resolving in multiple modules project
> --------------------------------------------------------
>
> Key: MENFORCER-304
> URL: https://issues.apache.org/jira/browse/MENFORCER-304
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
> Affects Versions: 3.0.0-M1
> Reporter: Zhenlei Huang
> Assignee: Elliotte Rusty Harold
> Priority: Minor
> Fix For: 3.0.0
>
>
> In a multiple modules project, some enforcer rule can not get sufficient
> dependency info with default phase validate, causing issues like
> [https://issues.apache.org/jira/browse/MENFORCER-168|https://issues.apache.org/jira/browse/MENFORCER-168],
> and probable
> [https://issues.apache.org/jira/browse/MNG-3283|https://issues.apache.org/jira/browse/MNG-3283]
> Proposal: Include dependencies of reactor projects (not yet compiled) during
> rule dependency resolving.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
