[ 
https://issues.apache.org/jira/browse/MNG-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432614#comment-16432614
 ] 

Karl Heinz Marbaise edited comment on MNG-6391 at 4/10/18 5:21 PM:
-------------------------------------------------------------------

This is intentional to have them also at the last module in reactor. This is 
useful in particular if you have a large build with many modules that you get 
information on the last module as well and not only at the beginning of the 
reactor list...otherwise you have to scrolle to much...See also the [release 
notes|https://maven.apache.org/docs/3.5.3/release-notes.html] which describes 
that behaviour.

The reactor order is defined by the dependencies between the module which is 
independent of the order you have defined the modules list in your pom file...


was (Author: khmarbaise):
This is intentional to have them also at the last module in reactor. This is 
useful in particular if you have a large build with many modules that you get 
information on the last module as well and not only at the beginning of the 
reactor list...otherwise you have to scrolle to much...See also the [release 
notes|https://maven.apache.org/docs/3.5.3/release-notes.html] which describes 
that behaviour.

> Printout version of last built module in reactor build
> ------------------------------------------------------
>
>                 Key: MNG-6391
>                 URL: https://issues.apache.org/jira/browse/MNG-6391
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.3
>            Reporter: Alexander Griesbaum
>            Assignee: Karl Heinz Marbaise
>            Priority: Major
>
> MNG-6352 introduced printout of the version in a reactor build.
> If I build a multi-module project, not just the parent has the version 
> printout but also the last built module.
> {code:java}
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] parent 4.0.0-SNAPSHOT ......................... SUCCESS [ 3.610 s]
> [INFO] parent-lib .................................... SUCCESS [ 0.492 s]
> [INFO] commons ....................................... SUCCESS [ 25.444 s]
> [INFO] loadbalancer-starter .......................... SUCCESS [ 21.198 s]
> [INFO] proxy-config-starter 4.0.0-SNAPSHOT ........... SUCCESS [ 7.496 s]
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] 
> ------------------------------------------------------------------------
> {code}
> If I remove the "proxy-config-starter" module, "loadbalancer-starter" got the 
> version printout.
> Also this is not the order I configured the modules in the parent pom but I 
> think this could be something on my side.
> {code:java}
> <modules>
>     <module>commons</module>
>     <module>loadbalancer-starter</module>
>     <module>parent-lib</module>
>     <module>proxy-config-starter</module>
> </modules>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to