[jira] Commented: (MNG-2570) Maven needs to support multiple logging levels

[Costin Caraivan (JIRA)]

[ 
http://jira.codehaus.org/browse/MNG-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=247859#action_247859
 ] 

Costin Caraivan commented on MNG-2570:
--

I'm not sure it's the same thing as mentioned by the original reporter, but 
from what I saw while working with Maven and from what I see the developers 
needing, the default mode is ok (verbose).

The debug modes should be:
-X, --debug - default debug output, without classloading information (no 
dependencies, and especially no managed dependencies)
-Xd, --extra-debug - extra debug information, the current -X

The current debug mode usually has something like 1% useful information while 
debugging plugin problems, configuration problems. We have hundreds of 
thousands of lines of lines showing managed/transitive dependencies for big 
builds, when all we want to see is: what was the real parameter used by Maven 
when launching the jarsigner (for example)...

 Maven needs to support multiple logging levels
 --

 Key: MNG-2570
 URL: http://jira.codehaus.org/browse/MNG-2570
 Project: Maven 2  3
  Issue Type: Improvement
  Components: Logging
Affects Versions: 2.0.4
Reporter: Brian Fox
 Fix For: Issues to be reviewed for 3.x


 The current logging levels are essentially verbose (default) and debug (-X). 
 We need a slightly less verbose output so that things like compiler warnings 
 and other output is actually visable to the developer. Currently it gets 
 buried in all the noise.

-- 
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-2570) Maven needs to support multiple logging levels

[Asgeir S. Nilsen (JIRA)]

[ 
http://jira.codehaus.org/browse/MNG-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92666
 ] 

Asgeir S. Nilsen commented on MNG-2570:
---

What would it take to change the LoggerManager from ConsoleLoggerManager to for 
instance Log4JLoggerManager, and enable log4j configuration of Maven's logging?

This would enable different levels of logging for different components, and 
also different appenders.

Would it suffice to drop one of the plexus-logging jars in M2_HOME/lib ?

There is some information at 
http://plexus.codehaus.org/writing-components-trial/05_01_custom_logging_implementation.html,
 but I'm not sufficiently experienced with Maven's innards to determine what 
needs to be done..

 Maven needs to support multiple logging levels
 --

 Key: MNG-2570
 URL: http://jira.codehaus.org/browse/MNG-2570
 Project: Maven 2
  Issue Type: Improvement
  Components: Logging
Affects Versions: 2.0.4
Reporter: Brian Fox

 The current logging levels are essentially verbose (default) and debug (-X). 
 We need a slightly less verbose output so that things like compiler warnings 
 and other output is actually visable to the developer. Currently it gets 
 buried in all the noise.

-- 
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