[
https://issues.apache.org/jira/browse/MNG-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236773#comment-17236773
]
Martin Kanters commented on MNG-7026:
-------------------------------------
Thanks for coming back so quickly. I do not work with such big projects, so I
do not share your experience, but I do understand what you mean now.
One thing is on my mind. In the case that you have these projects: C depends on
B depends on A. You mean that if you change A, you only want to rebuild B and
not C using something like -amd.
While it's less common, it's possible that C could fail by the changes A
introduces. Is that something that you don't mind in your use-case?
> Ability to only build direct dependants
> ---------------------------------------
>
> Key: MNG-7026
> URL: https://issues.apache.org/jira/browse/MNG-7026
> Project: Maven
> Issue Type: New Feature
> Components: Command Line, core
> Affects Versions: 3.6.3
> Reporter: Chadi
> Priority: Minor
> Labels: easyfix, features
>
> We are an organization with a large reactor. When we update a project X, we
> would like to have the possibility to compile the artifacts that directly
> depend on X, without having to recompile everything.
> The fix itself is trivial and consists of traversing in non-recursive mode. I
> can prepare a PR if you are OK with the request.
> Its activation could be done using a flag such as --amdd,
> --also-make-direct-dependents, or maybe --also-make-dependents=direct
> What do you think?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
