You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2022/10/20 15:31:00 UTC

[jira] [Resolved] (IMPALA-11673) Exclude spring-jcl from the classpath

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

Joe McDonnell resolved IMPALA-11673.
------------------------------------
    Fix Version/s: Impala 4.2.0
       Resolution: Fixed

> Exclude spring-jcl from the classpath
> -------------------------------------
>
>                 Key: IMPALA-11673
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11673
>             Project: IMPALA
>          Issue Type: Task
>          Components: Frontend
>    Affects Versions: Impala 4.2.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Critical
>             Fix For: Impala 4.2.0
>
>
> The dependency on spring-core brings in spring-jcl, which is intended as a replacement for the commons-logging framework. spring-jcl implements classes that overlap with commons-logging (which Impala also has on its classpath).
> https://github.com/spring-projects/spring-framework/issues/20611#issuecomment-453462024
> It doesn't seem useful to have spring-jcl around, so let's exclude it to avoid this overlap.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)