You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Rafał Figas (JIRA)" <ji...@apache.org> on 2018/06/26 14:29:00 UTC
[jira] [Commented] (MENFORCER-304) Improve dependency resolving in
multiple modules project
[ https://issues.apache.org/jira/browse/MENFORCER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523802#comment-16523802 ]
Rafał Figas commented on MENFORCER-304:
---------------------------------------
I belive this proposal is very good. In my case there is a multimodule project that has 2 modules:
* first is responsible for building webapp (war)
* second is responsible for tests - it takes war built by first module, and deploys with cargo, makes some tests etc.
Unfortunately, now, while enforcer goal at second module I receive dependency resolve failure, as this war is not yet deployed to any repository, thus it cannot be resolved. I believe that this proposal should fix such cases.
> 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)