You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Volkan Yazici (Jira)" <ji...@apache.org> on 2020/11/26 11:04:00 UTC
[jira] [Commented] (MNG-7036) Avoid non-compile goals (e.g., test)
for --also-make introduced modules
[ https://issues.apache.org/jira/browse/MNG-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239194#comment-17239194 ]
Volkan Yazici commented on MNG-7036:
------------------------------------
See [the related StackOverflow post|https://stackoverflow.com/q/65004670/1278899].
> Avoid non-compile goals (e.g., test) for --also-make introduced modules
> -----------------------------------------------------------------------
>
> Key: MNG-7036
> URL: https://issues.apache.org/jira/browse/MNG-7036
> Project: Maven
> Issue Type: Improvement
> Reporter: Volkan Yazici
> Priority: Minor
>
> 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}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)