[
https://issues.apache.org/jira/browse/MNG-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236742#comment-17236742
]
Chadi commented on MNG-7026:
----------------------------
Thanks Martin for the quick feedback.
Perhaps it might not be needed with smaller projects, but in our case, we have
thousands of projects and having this would be highly beneficial.
Using exclusions as you're suggesting, or explicitly listing the projects in a
multi-module pom is an issue because those have to be explicitly maintained and
continuously updated.
Basically X is a client project. I need to make changes to X, and by using -amd
alone, it recompiles the whole tree of dependents. But my dependencies are
clean, so by having something like -amd+direct, I make sure that I only compile
projects that use X, and no more. This is very helpful for development
purposes, or even in a (give-me-a-quick-feedback) CI context where I'm looking
for a build result without having to build the whole reactor.
> 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)
