You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2026/06/03 07:48:00 UTC

[jira] [Resolved] (IMPALA-14917) Centralize Junit version across modules

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

Stamatis Zampetakis resolved IMPALA-14917.
------------------------------------------
    Fix Version/s: Impala 5.0.0
       Resolution: Fixed

> Centralize Junit version across modules
> ---------------------------------------
>
>                 Key: IMPALA-14917
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14917
>             Project: IMPALA
>          Issue Type: Task
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>             Fix For: Impala 5.0.0
>
>         Attachments: dep-tree.txt
>
>
> Currently there are three different Junit versions used in the project:
> * junit:junit:jar:4.13.2
> * junit:junit:jar:4.12
> * junit:junit:jar:4.10
> Some are declared explicitly in Impala and other are coming transitively.  To make matters worse in some cases the dependency is also present in the compile/runtime classpath making it part of the engine.
> For more details check dep-tree.txt file
> {noformat}
> mvn dependency:tree -Dincludes=junit:* > dep-tree.txt
> {noformat}
> I bumped into this while I was trying to understand why certain code compiles in some modules and not in others. Obviously different versions == different features == different APIs.



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