[Commented] (MENFORCER-304) Improve dependency resolving in multiple modules project

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Commented] (MENFORCER-304) Improve dependency resolving in multiple modules project

Tibor Digana (Jira)

    [ https://issues.apache.org/jira/browse/MENFORCER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125933#comment-17125933 ]

Hudson commented on MENFORCER-304:
----------------------------------

Build failed in Jenkins: Maven TLP » maven-enforcer » master #135

See https://builds.apache.org/job/maven-box/job/maven-enforcer/job/master/135/

> 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
(v8.3.4#803005)