You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2022/01/04 06:41:00 UTC

[jira] [Updated] (CALCITE-4971) update httpclient and httpcore to latest 5.1 release

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

Istvan Toth updated CALCITE-4971:
---------------------------------
    Description: 
Apache commons httpclient/httpcomponent 4.5 depend on commons-logging and not slf4j. This means that phoenix-thin requires explicit log4j configuration to work.

We want all logging to go through SLF4j, and to be able to use any supported backend.

Based on an an offline conversation with [~elserj]

As these are new major version, it's probably going to involve more than a version bump.

  was:
Apache commons httpclient/httpcomponent 4.5 depend on commons-logging and not slf4j. This means that phoenix-thin requires explicit log4j configuration to work.

We want all logging to go through SLF4j, and to be able to use any supported backend.

Based on an an offline conversation with [~elserj]

        Summary: update httpclient and httpcore to latest 5.1 release  (was: Update  org.apache.httpcomponents:httpclient to latest)

> update httpclient and httpcore to latest 5.1 release
> ----------------------------------------------------
>
>                 Key: CALCITE-4971
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4971
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica
>            Reporter: Istvan Toth
>            Priority: Major
>
> Apache commons httpclient/httpcomponent 4.5 depend on commons-logging and not slf4j. This means that phoenix-thin requires explicit log4j configuration to work.
> We want all logging to go through SLF4j, and to be able to use any supported backend.
> Based on an an offline conversation with [~elserj]
> As these are new major version, it's probably going to involve more than a version bump.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)