[
http://jira.codehaus.org/browse/MNG-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3381:
------------------------------
Fix Version/s: 2.1
Component/s: Logging
> 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: http://jira.codehaus.org/browse/MNG-3381
> Project: Maven 2
> Issue Type: Improvement
> Components: Logging, Plugins and Lifecycle
> Affects Versions: 2.0.8, 2.1-alpha-1
> Reporter: John Casey
> Fix For: 2.1
>
>
> 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 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
