[
https://issues.apache.org/jira/browse/MENFORCER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480521#comment-16480521
]
ASF GitHub Bot commented on MENFORCER-304:
------------------------------------------
gmshake opened a new pull request #35: [MENFORCER-304] Improve dependency
resolving in multiple modules project
URL: https://github.com/apache/maven-enforcer/pull/35
see
[https://issues.apache.org/jira/browse/MENFORCER-304](https://issues.apache.org/jira/browse/MENFORCER-304)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
> Priority: Minor
>
> 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
(v7.6.3#76005)
