Maven 2 & 3

Maven needs to support multiple logging levels

Details

  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

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.

Issue Links

is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. MNG-4935 Filter classloader information in debug output (or create a new debug switch)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

New Feature - A new feature of the product, which has yet to be developed. MNG-5397 Use SLF4J for logging

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

New Feature - A new feature of the product, which has yet to be developed. MNG-113 logging levels

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Improvement - An improvement or enhancement to an existing feature or task. MNG-3463 AsbtractMojo should look for LoggerManager plexus component

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MNG-4505 use slf4j to control various logging frameworks

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MNG-5239 Maven integration developers would like to be able to override the maven logging appender.

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Asgeir S. Nilsen added a comment -

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

Show
Asgeir S. Nilsen added a comment - 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..
Hide
Permalink
Costin Caraivan added a comment - - edited

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 could be improved, however, for example:
-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)...

Show
Costin Caraivan added a comment - - edited 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 could be improved, however, for example: -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)...
Hide
Permalink
patrick garcia added a comment -

As a simple answer to this issue, you will find in the attached patch a new "w" "-warinig" maven option. This set the log level to LOGGING_LEVEL_WARN

The final solution for this issue may be cleverer. At least this patch allows setting ALL possible log level values.

Integration test are ok.

more over, I have tested it by checking the following commands:
$M2_HOME/bin/mvn --help
$M2_HOME/bin/mvn -w test
$M2_HOME/bin/mvn --warning test

Then I did a diff with the following commands:
$M2_HOME/bin/mvn test
$M2_HOME/bin/mvn -q test

Show
patrick garcia added a comment - As a simple answer to this issue, you will find in the attached patch a new " w" " -warinig" maven option. This set the log level to LOGGING_LEVEL_WARN The final solution for this issue may be cleverer. At least this patch allows setting ALL possible log level values. Integration test are ok. more over, I have tested it by checking the following commands: $M2_HOME/bin/mvn --help $M2_HOME/bin/mvn -w test $M2_HOME/bin/mvn --warning test Then I did a diff with the following commands: $M2_HOME/bin/mvn test $M2_HOME/bin/mvn -q test

People

  • Assignee:
    Unassigned
    Reporter:
    Brian Fox
Vote (26)
Watch (20)

Dates

  • Created:
    Updated: