[
https://jira.codehaus.org/browse/MNG-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343396#comment-343396
]
Luuk van den Broek commented on MNG-5230:
------------------------------------------
Nested modules are not excluded by parent module.
The exclusion method mimics the inclusion method and its matcher does not
support wildcards etc.
So to cascade exclusion would necessitate an extra flag like -amd.
The dependency graph is filtered in the following order when using -pl:
1. included projects + possibly upstream and downstream
2. excluded projects
3. skipping for resume projects
So it should be possible to directly exclude nested modules as they should be
present in the intial dependency graph before filtering starts.
Could you share your setup and how you are invoking the build?
> Command line option to exclude modules from reactor
> ---------------------------------------------------
>
> Key: MNG-5230
> URL: https://jira.codehaus.org/browse/MNG-5230
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Command Line
> Affects Versions: 3.0.3
> Reporter: Falko Modler
> Assignee: Robert Scholte
> Fix For: 3.2.1
>
> Attachments: MNG-5230-maven-core.patch,
> MNG-5230-maven-integration-testing.patch
>
>
> Every now and then I want to exclude one or more modules from a rather large
> reactor build.
> One reason for this can be: The respective module has tests that take long
> time to execute and I know that I don't need to execute them.
> Introducing yet another profile for this is not desirable for various reasons.
> So, something like an opposite to -pl would come in handy. Let's say "-el"
> for "exclude list".
> Example:
> {code}
> root
> + module a
> + module a1
> + module a2
> + module b
> + module b1
> + module c
> {code}
> Calling _mvn -el a1,c_ would build all modules execpt a1 and c.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
