[
https://issues.apache.org/jira/browse/MNG-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316101#comment-17316101
]
Hudson commented on MNG-7112:
-----------------------------
Build unstable in Jenkins: Maven » Maven TLP » maven-studies » maven-metrics #18
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-studies/job/maven-metrics/18/
> --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)
