[
https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973399#comment-14973399
]
Axel Fontaine commented on MNG-5916:
------------------------------------
The main thing I want have turned off here is the wire logger of the HTTP
client.
My point isn't that this should affect the entire build, but that there should
be a mechanism of doing this on a plugin by plugin base if necessary. This was
possible before and this should probably be doable as each plugin already has
some level of isolation by having its own classloader.
I would be happy with any solution that re-enables what was available with 3.0.
P.S.: The wire logger makes very little sense and Gradle for example has it set
to off by default. Would shipping Maven with it off by default be possible?
> 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)
