[jira] [Commented] (BIGTOP-4070) Compilation Failure of Ranger 2.4 on Maven 3.8

["Masatake Iwasaki (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835766#comment-17835766 ] 

Masatake Iwasaki commented on BIGTOP-4070:
------------------------------------------

I could not reproduce the issue by Maven 3.8.8 installed by bigtop_toolchain on Ubuntu 22.04.

> Compilation Failure of Ranger 2.4 on Maven 3.8
> ----------------------------------------------
>
>                 Key: BIGTOP-4070
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-4070
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: caijialiang
>            Assignee: caijialiang
>            Priority: Major
>         Attachments: image-2024-03-01-13-40-59-603.png, image-2024-03-01-13-41-20-505.png
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Issue: ranegr 2.4 can be compiled successfully in Maven 3.6, but fails in Maven 3.8.
> !image-2024-03-01-13-40-59-603.png!
> Due to improvements made in Maven versions after 3.6, the `kafka.version` setting can affect the versions of dependencies in the global JAR files.
>  
> Kylin-server-base ultimately depends on `org.apache.kafka`. When compiled in Maven 3.6, it resolves to `org.apache.kafka:kafka_2.11:2.1.1`. However, in Maven 3.8, it attempts to find `org.apache.kafka:kafka_2.11:2.8.2`, which does not exist in Maven repositories.
> Maven 3.8 introduces a new feature that rigorously handles dependency versions defined in the global POM file. Dependency versions defined in the global POM file take precedence over project-specific versions, potentially overriding explicitly specified versions. This stricter version propagation rule can lead to different dependency resolution behavior in Maven 3.8 compared to Maven 3.6.
> Therefore, in Maven 3.8, the `kafka.version` defined in the global POM affects the Kafka version in kylin-server-base, leading to compilation failure. Adding dependency management can resolve this issue.
> !image-2024-03-01-13-41-20-505.png!



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