Stamatis Zampetakis created IMPALA-14917:
--------------------------------------------
Summary: 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
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)
