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

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

I don't think the issue is about not understanding the reactor build. It simply 
looks awkard that the final entry has a version number, even if it is similar 
to the module before. 
I assume we all agree the first one makes sense. The *only* reason the last one 
is printed with a version here is because the list of modules might be long, 
which means you need to scroll to the first entry. It has nothing to do with 
the context of the module, but it does look like that, as if there is something 
special with this module.
Adding a version to every line makes  would be correct but makes it much harder 
to read.
There's another option: remove it from the last line and accept that with large 
projects one need to scroll a little bit. But at least there's no confusion.

> 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: Improvement
>          Components: core
>    Affects Versions: 3.5.3
>            Reporter: Alexander Griesbaum
>            Assignee: Karl Heinz Marbaise
>            Priority: Minor
>             Fix For: 3.5.4
>
>
> 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