[
https://issues.apache.org/jira/browse/MNG-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193098#comment-17193098
]
Martin Kanters commented on MNG-6981:
-------------------------------------
This feature seemed to be easy to implement and has limited effect on existing
integration tests:
- [https://github.com/apache/maven/pull/374]
- [https://github.com/apache/maven-integration-testing/pull/71]
One caveat is that --non-recursive has effect on the pom file on the
MavenExecutionRequest (meaning: the pom.xml in the working directory or a pom
file specified with -f).
When --non-recursive is used, only that specific pom file is collected as
project. So, the reactor can only consist of that project. This results in that
--pl cannot be combined with --non-recursive. (-f can though, see [integration
testing PR|https://github.com/apache/maven-integration-testing/pull/71]).
> Add --recursive option
> ----------------------
>
> Key: MNG-6981
> URL: https://issues.apache.org/jira/browse/MNG-6981
> Project: Maven
> Issue Type: New Feature
> Components: Command Line
> Affects Versions: 3.6.3
> Reporter: Knut Wannheden
> Priority: Major
>
> Since there is already a {{\--non-recursive}} option a new {{\--recursive}}
> option might be confusing, but let me explain my use case. I often use the
> {{-pl}} option and in a multi-module Maven project with more than just two
> "levels", I would like to be able to build a project (or set of projects)
> including all child-modules. This is, AFAIK, currently not possible and what
> I would like to use the new {{\--recursive}} (or similar) option for.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
