[jira] (MNG-3381) Create a mojo Log to accumulate warning (and higher log-level) messages per project, and output them like error reports in the summary.

["Paul Benedict (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MNG-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict updated MNG-3381:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> Create a mojo Log to accumulate warning (and higher log-level) messages per project, and output them like error reports in the summary.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3381
>                 URL: https://jira.codehaus.org/browse/MNG-3381
>             Project: Maven
>          Issue Type: Improvement
>          Components: Logging, Plugins and Lifecycle
>    Affects Versions: 2.0.8, 3.0-alpha-1
>            Reporter: John Casey
>
> currently, it's a mojo's choice whether to throw a MojoExecutionException or MojoFailureException and stop the build when something comes up during its own execution. In many cases, mojos choose to output ERROR or WARNING messages, but these often are drowned in the sheer volume of INFO output to the console.
> Look into modifying the default mojo Log class to record anything above INFO for recovery later by the CLI reporter methods, so ERROR and WARNING output can be added to the summary for that project.
> Possibly even a good idea to adjust the summary pronouncement (BUILD SUCCESSFUL, BUILD FAILED) to reflect the presence of this sort of output:
> BUILD SUCCESSFUL, with warnings
> or something similar.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)