[
https://issues.apache.org/jira/browse/MNG-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448837#comment-16448837
]
Karl Heinz Marbaise commented on MNG-6391:
------------------------------------------
So after thinking about this what about this and removing the version
information from the reactor summary completely and add a supplemental line
with the version information.
{code}
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] parent ........................................ 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 .......................... SUCCESS [ 7.496 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Version: 4.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:45 min
[INFO] Finished at: 2018-04-11T09:56:21+02:00
[INFO] ------------------------------------------------------------------------
{code}
For case where we have an aggregator we can add the version to each line in
{{Reactor Summary}} that will also make clear we have an aggregator instead of
a multi module build with the same version..WDYT ?
> 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)