[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Kalnichevski resolved HTTPCLIENT-1082.
-------------------------------------------

    Resolution: Invalid

Severin

HttpClient does not use or in any way depend on Avalon LogKit. It uses Commons 
Logging API, which is an abstraction layer than can be configured to use 
different logging back-ends such as java.util.logging. One could potentially 
replace Commons Logging with a more modern framework such as SLF4J but there is 
no great urgency to do so as SLF4J is 100% compatible with Commons Logging and 
can be used as a drop-in replacement.

Please make sure you are using version 1.1.1 of commons-logging. Older versions 
had a problem with some optional dependencies not being declared as such in 
pom.xml (See LOGGING-113). I suspect this may be the reason why you are seeing 
Avalon LogKit on your project classpath.

Oleg

> httpcomponents HttpClient should use recent logging framework such as 
> java.util.logging
> ---------------------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1082
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1082
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient
>    Affects Versions: 4.1.1
>         Environment: Fedora 15.
>            Reporter: Severin Gehwolf
>
> httpcomponents httpclient uses org.apache.log and 
> org.apache.avalon.framework, which are quite old and the avalon project has 
> been closed. It would make sense to get rid of such old logging framework 
> dependencies and replace it by newer ones, such as java.util.logging
> Thanks!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to