maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Axel Fontaine (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5916) Regression from 3.0: Allow filtering out certain loggers from within a plugin
Date Sun, 25 Oct 2015 19:29:27 GMT

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

Axel Fontaine commented on MNG-5916:
------------------------------------

You can define regression how you want, but fact is it was working (and very useful) with
Maven 3.0 and it isn't anymore now. I am open for any alternative solutions to this problem,
including shipping better defaults for the http client wire logger (always off) as suggested
above and implemented by Gradle.

> Regression from 3.0: Allow filtering out certain loggers from within a plugin
> -----------------------------------------------------------------------------
>
>                 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