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

Robert Scholte commented on MNG-6391:
-------------------------------------

I also had a little bit of trouble and I understand the confusion. The first 
makes sense, but the last is questionable. I understand the reason, but I can 
imagine we should look for a more logic solution.
I can think of 2 solution
- add a summary-line at the end.
- add the version to the BUILD SUCCESS

or leave it like it is.

> 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