[MNG-7036] Avoid non-compile goals (e.g., test) for --also-make introduced modules
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Volkan Yazici](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vy)** opened **[MNG-7036](https://issues.apache.org/jira/browse/MNG-7036?redirect=false)** and commented
It is a common practice to execute goals for a single module, e.g., `mvn \-pl son verify`. Though if there exists a dependency to another module, one needs to provide the extra `\-am (\-\-also\-make)` flag, which repeats the requested goal for the dependency modules too. This is not a desirable behavior in many circumstances. For instance, consider: `mvn \-am \-pl son verify`. Here it is highly likely that the user only wants to verify `son`, not its dependencies.
I would really appreciate an extra configuration property to avoid executing non-compile goals on dependencies introduced by `\-\-also\-make`.
---
No further details from [MNG-7036](https://issues.apache.org/jira/browse/MNG-7036?redirect=false)
Contributor guide
Assessment
This issue has not been assessed yet.