[jira] Created: (MNG-4828) avoid the reactor summary when it isn't helpful

["Brett Porter (JIRA)" <ji...@codehaus.org>]

avoid the reactor summary when it isn't helpful
-----------------------------------------------

                 Key: MNG-4828
                 URL: http://jira.codehaus.org/browse/MNG-4828
             Project: Maven 2 & 3
          Issue Type: Improvement
          Components: Logging
    Affects Versions: 3.0-beta-3
            Reporter: Brett Porter
            Priority: Minor


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

{code}
mvn help:describe -Dplugin=surefire
{code}

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:

{code}
[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] ------------------------------------------------------------------------
{code}

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

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


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira