[jira] [Commented] (MNG-6391) Printout version of last built module in reactor build

2018-04-18 Thread Alexander Griesbaum (JIRA)

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

Alexander Griesbaum commented on MNG-6391:
--

Hi [~michael-o],

The order has nothing to do with this visual misleading information. I mixed it 
up because I did not understand that the reactor build changes order to resolve 
dependencies and so I assumed that it could correlate with the visual "bug" I 
started the discussion about.

I am also fine with deleting the information at the end completly but I think 
it is pretty obvious that the actual solution is not that good.

> 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}
> 
> commons
> loadbalancer-starter
> parent-lib
> proxy-config-starter
> 
> {code}



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


[jira] [Commented] (MNG-6391) Printout version of last built module in reactor build

2018-04-11 Thread Alexander Griesbaum (JIRA)

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

Alexander Griesbaum commented on MNG-6391:
--

Hi, sorry for not reading the release notes properly, I created the issue based 
on the 
[example|https://issues.apache.org/jira/browse/MNG-6352?focusedCommentId=16367736=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16367736]
 in MNG-6352.

The current solution is still confusing in my opinion so I am with Robert: a 
new line at the bottom or additional info at the BUILD SUCCESS line.

Info at BUILD SUCCESS:
{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 .. SUCCESS [ 7.496 s]
[INFO] 
[INFO] BUILD SUCCESS 4.0.0-SNAPSHOT
[INFO] 
[INFO] Total time: 01:45 min
[INFO] Finished at: 2018-04-11T09:56:21+02:00
[INFO] 
{code}
Info in a separate line (Didn't use "Version Summary" to not being too verbose):
{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 .. SUCCESS [ 7.496 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 01:45 min
[INFO] Finished at: 2018-04-11T09:56:21+02:00
[INFO] Version: 4.0.0-SNAPSHOT
[INFO] 
{code}
 

What do you think about it?

> 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}
> 
> commons
> loadbalancer-starter
> parent-lib
> proxy-config-starter
> 
> {code}



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


[jira] [Created] (MNG-6391) Printout version of last built module in reactor build

2018-04-10 Thread Alexander Griesbaum (JIRA)
Alexander Griesbaum created MNG-6391:


 Summary: 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


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}

commons
loadbalancer-starter
parent-lib
proxy-config-starter

{code}



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