Maven 2 & 3

avoid the reactor summary when it isn't helpful

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 3.0-beta-3
  • Fix Version/s: None
  • Component/s: Logging
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

At the root of a large multi-module project (eg, Redback), run:

mvn help:describe -Dplugin=surefire

The output is lost among the scanning + summary, even though it will only ever affect one project.

In a scenario like this, I think the reach summary should be reduced to:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Redback ........................................... SUCCESS [5.922s]
[INFO]         Sub-modules not executed
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.777s
[INFO] Finished at: Sun Sep 19 10:35:40 PDT 2010
[INFO] Final Memory: 15M/81M
[INFO] ------------------------------------------------------------------------

And potentially reduce the start to (though I'm not sure if it's known at the point it's shown):

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] Redback
[INFO] (Sub-modules will not be executed)
[INFO] ------------------------------------------------------------------------

Activity

No work has yet been logged on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Brett Porter
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: