You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ittay Dror (JIRA)" <ji...@codehaus.org> on 2008/07/03 09:17:26 UTC
[jira] Created: (MNG-3648) Maven is too verbose in its output,
obscuring actual messages
Maven is too verbose in its output, obscuring actual messages
-------------------------------------------------------------
Key: MNG-3648
URL: http://jira.codehaus.org/browse/MNG-3648
Project: Maven 2
Issue Type: Improvement
Affects Versions: 2.0.8
Reporter: Ittay Dror
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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3648) Maven is too verbose in its output,
obscuring actual messages
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204365#action_204365 ]
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: http://jira.codehaus.org/browse/MNG-3648
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3648) Maven is too verbose in its output,
obscuring actual messages
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3648:
------------------------------
Fix Version/s: 2.1
Component/s: Logging
> Maven is too verbose in its output, obscuring actual messages
> -------------------------------------------------------------
>
> Key: MNG-3648
> URL: http://jira.codehaus.org/browse/MNG-3648
> Project: Maven 2
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 2.0.8
> Reporter: Ittay Dror
> Fix For: 2.1
>
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3648) Maven is too verbose in its output,
obscuring actual messages
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-3648.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.x)
3.0-alpha-6
> Maven is too verbose in its output, obscuring actual messages
> -------------------------------------------------------------
>
> Key: MNG-3648
> URL: http://jira.codehaus.org/browse/MNG-3648
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira