[
https://jira.codehaus.org/browse/MNG-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342726#comment-342726
]
Norbert Wnuk commented on MNG-5597:
-----------------------------------
Attaching sample project to present limitation when -pl, -am, -amd options are
not enough to fully and automatically rebuild entire submodule in multi-module
project - (b), (c), (d). There is no other way to fully rebuild module-a
(including downstream dependency to module-b outside of module-a's subtree)
other than option (e) which requires explicit projects list specification. This
behavior is consistent with documentation (-am, -amd options invoked
separately) but not well documented and therefore may be misleading in complex
projects.
(a) mvn clean install
------------------------------------------------------------------------
Reactor Summary:
top-level-parent .................................. SUCCESS [ 0.453 s]
module-b .......................................... SUCCESS [ 1.258 s]
module-a-parent ................................... SUCCESS [ 0.011 s]
module-a1 ......................................... SUCCESS [ 0.072 s]
module-a2 ......................................... SUCCESS [ 0.068 s]
module-c .......................................... SUCCESS [ 0.086 s]
------------------------------------------------------------------------
BUILD SUCCESS
------------------------------------------------------------------------
(b) mvn -pl module-a clean install
------------------------------------------------------------------------
BUILD SUCCESS
------------------------------------------------------------------------
(c) mvn -pl module-a -am clean install
------------------------------------------------------------------------
Reactor Summary:
top-level-parent .................................. SUCCESS [ 0.503 s]
module-a-parent ................................... SUCCESS [ 0.010 s]
------------------------------------------------------------------------
BUILD SUCCESS
------------------------------------------------------------------------
(d) mvn -pl module-a -am -amd clean install // module-b is ignored
------------------------------------------------------------------------
Reactor Summary:
top-level-parent .................................. SUCCESS [ 0.455 s]
module-a-parent ................................... SUCCESS [ 0.010 s]
module-a1 ......................................... SUCCESS [ 1.275 s]
module-a2 ......................................... SUCCESS [ 0.069 s]
------------------------------------------------------------------------
BUILD SUCCESS
------------------------------------------------------------------------
(e) mvn -pl module-a/module-a1,module-a/module-a2 -am clean install
------------------------------------------------------------------------
Reactor Summary:
top-level-parent .................................. SUCCESS [ 0.453 s]
module-b .......................................... SUCCESS [ 1.187 s]
module-a-parent ................................... SUCCESS [ 0.018 s]
module-a1 ......................................... SUCCESS [ 0.075 s]
module-a2 ......................................... SUCCESS [ 0.072 s]
------------------------------------------------------------------------
BUILD SUCCESS
------------------------------------------------------------------------
> Provide documentation for the behaviour of the reactor as a result of recent
> changes
> ------------------------------------------------------------------------------------
>
> Key: MNG-5597
> URL: https://jira.codehaus.org/browse/MNG-5597
> Project: Maven 2 & 3
> Issue Type: Improvement
> Affects Versions: 3.2.1
> Reporter: Jason van Zyl
> Fix For: 3.2.2
>
>
> Specifically how it relates to MNG-5557, MNG-5582, and MNG-5578
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
