maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Hammar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
Date Sun, 25 Oct 2015 13:06:27 GMT

    [ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973229#comment-14973229
] 

Anders Hammar commented on MNG-5916:
------------------------------------

[~axel.fontaine]Could you please attach a project or similar for us to reproduce the issue?
You're probably aware of it but just to be clear, the logging was changed in v3.1 of Maven
core and what you're experiencing is likely due to this.
Also, possibly the issue should be changed to an improvement based on the wording in the title.

> Replace slf4j-simple with logback or allow filtering out certain loggers
> ------------------------------------------------------------------------
>
>                 Key: MNG-5916
>                 URL: https://issues.apache.org/jira/browse/MNG-5916
>             Project: Maven
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 3.3.3
>            Reporter: Axel Fontaine
>
> We are developing a Maven plugin that uses Apache HTTP client. When switching Maven to
debug mode with -X Apache HTTP client produces gazillions of output messages as all wire traffic
is being logged. It is not only annoying, it also makes this unusable in systems like Travis
CI that limit output to some sane amount..
> We need some way of disabling the output of the org.apache.http.wire log from our within
our plugin jar. (Patching existing Maven installations is not an option as we do not have
this kind of control over our user's machines).
> Any help/suggestions/solutions welcome.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message