maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <>
Subject [jira] Commented: (MNG-3648) Maven is too verbose in its output, obscuring actual messages
Date Tue, 29 Dec 2009 02:39:55 GMT


Jason van Zyl commented on MNG-3648:

Output is a lot better in 3.0.

> Maven is too verbose in its output, obscuring actual messages
> -------------------------------------------------------------
>                 Key: MNG-3648
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Logging
>    Affects Versions: 2.0.8
>            Reporter: Ittay Dror
>             Fix For: 3.0-alpha-6
> Things I would like to move to 'debug' or 'trace' levels:
> 1. Reactor build order list: the order is always the same, so why print? if it's an issue
of telling the user, in case he forgot to trigger a profile, then i think that in most cases
it misses the target, simply because it appears so much that people just don't pay attention
to the list
> 2. Reactor summary: showing successful modules means it's harder to find the failed ones.
Just show me what failed. 
> 3. Plugins usually print they are running in 'info' level. This is actually a tracing
message as they will always run.
> I know I can suppress these with '-q', but then it suppresses all 'info' messages, so
that relevant information about actions taken (actions that change in each build) is not printed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message