You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Zhenlei Huang (JIRA)" <ji...@apache.org> on 2018/05/18 11:20:00 UTC
[jira] [Updated] (MENFORCER-304) Improve dependency resolving in
multiple modules project
[ https://issues.apache.org/jira/browse/MENFORCER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhenlei Huang updated MENFORCER-304:
------------------------------------
Summary: Improve dependency resolving in multiple modules project (was: Improvement dependency resolving in multiple modules project)
> 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)