[
https://issues.apache.org/jira/browse/RANGER-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
caijialiang updated RANGER-4728:
--------------------------------
Attachment: image-2024-03-01-13-36-49-585.png
> Compilation Failure of Ranger 2.4 on Maven 3.8
> ----------------------------------------------
>
> Key: RANGER-4728
> URL: https://issues.apache.org/jira/browse/RANGER-4728
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Reporter: caijialiang
> Priority: Major
> Attachments: image-2024-03-01-13-35-02-631.png,
> image-2024-03-01-13-36-20-548.png, image-2024-03-01-13-36-49-585.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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
