You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Kanters (Jira)" <ji...@apache.org> on 2021/04/02 14:16:00 UTC
[jira] [Closed] (MNG-7112) --projects flag should honor
--non-recursive flag
[ https://issues.apache.org/jira/browse/MNG-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Kanters closed MNG-7112.
-------------------------------
Fix Version/s: 4.0.0-alpha-1
4.0.0
Resolution: Fixed
Done in [7c742c298b60f60b1f8b92e43e4952ee128a4cd0|https://github.com/apache/maven/commit/7c742c298b60f60b1f8b92e43e4952ee128a4cd0]
> --projects flag should honor --non-recursive flag
> -------------------------------------------------
>
> Key: MNG-7112
> URL: https://issues.apache.org/jira/browse/MNG-7112
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and workspace
> Affects Versions: 4.0.x-candidate
> Reporter: Martin Kanters
> Assignee: Martin Kanters
> Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> In MNG-6981 and MNG-7102 the behavior around selecting aggregate projects has changed.
> Now, when an aggregate is (de)selected, the aggregate project and all its children will be (de)selected in the reactor.
> Before, just the aggregate was (de)selected and children were not taken into account.
> Because there is no good workaround currently and there is a need for it, we should offer a way to bring the old behavior back.
> {{\-N}} or {{\--non-recursive}} is currently used to only select one project, and it will not take its children into account during project collection (before the reactor flags are applied).
> After discussion on the mailing list, the proposed implementation is to use {{\--non-recursive}} together with {{\--projects}} to restore the old non-recursive behavior we had before.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)