You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2021/01/12 16:41:00 UTC

[jira] [Closed] (MENFORCER-262) ReactorModuleConvergence, support more project types

     [ https://issues.apache.org/jira/browse/MENFORCER-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylwester Lachiewicz closed MENFORCER-262.
------------------------------------------
    Resolution: Auto Closed

> ReactorModuleConvergence, support more project types
> ----------------------------------------------------
>
>                 Key: MENFORCER-262
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-262
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>            Reporter: Jon Harper
>            Priority: Major
>
> Hi,
> currently, the rule can not run on projects that have a separate aggregator pom (unless the aggregator is the parent of the parent pom.., which is not natural for projects with parent/pom.xml, parent/aggregator/pom.xml), or projects whose versions are not identical for all the artifacts.
> In both these cases, it is desirable to ensure that dependencies on artifacts of the reactor resolve to the artifacts during the reactor. Ie that the reactor can run entirely with mvn package, not using intermediate mvn install.
> Maybe add more options like ignoreModuleDependencies?
> E.G ignoreDifferentVersions
> For the separate aggregator pom, you could have
> <ignoreMissingParent>parentGroupId:parentArtifactId>



--
This message was sent by Atlassian Jira
(v8.3.4#803005)