[
https://jira.codehaus.org/browse/MNG-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341627#comment-341627
]
Robert Scholte commented on MNG-2570:
-------------------------------------
In my opinion this shouldn't be closed yet. If something goes wrong and you
don't get enough info, you'd like to activate debug logging, but only for the
failing plugin.
My idea is to add an optional argument to the {{-X}} specifying the plugin or
plugin+goal.
This would give you fast and accurate logging. You could probably get the same
result by changing the logging.properties, but that's far from user friendly.
> Maven needs to support multiple logging levels
> ----------------------------------------------
>
> Key: MNG-2570
> URL: https://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
>
> Attachments: MNG-2570-maven-embedder.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
