[
https://issues.apache.org/jira/browse/MNG-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354039#comment-17354039
]
Hudson commented on MNG-7102:
-----------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven » checkstyle-next #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/checkstyle-next/12/
> Align exclude project behavior to include project behavior when using
> --project-list
> ------------------------------------------------------------------------------------
>
> Key: MNG-7102
> URL: https://issues.apache.org/jira/browse/MNG-7102
> Project: Maven
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 4.0.0, 4.0.0-alpha-1
> Reporter: Falko Modler
> Assignee: Martin Kanters
> Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> In [MNG-6981|https://issues.apache.org/jira/browse/MNG-6981] included
> aggregator projects (parent poms) the reactor will automatically include its
> child modules.
> [~famod] reported on the dev mailinglist that the exclude behavior (-pl
> !<proj>) does not do that at this moment, which it should.
> The issue should be easily fixable by changing the {{DefaultGraphBuilder}}
> and its unit tests.
> One point to note here is that I cannot think of a backwards compatible
> workaround for the old behavior (for MNG-6981 it is done using -f and -N).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
