Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.8, 3.0-alpha-1
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Logging, Plugins and Lifecycle
-
Labels:None
-
Number of attachments :
Description
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.
Activity
Brett Porter
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 2.1 [ 13142 ] | |
| Component/s | Logging [ 11455 ] |
Jason van Zyl
made changes -
| Fix Version/s | 3.x [ 13145 ] | |
| Fix Version/s | 3.0 [ 13142 ] |