Sercan Tekin created HIVE-30039:
-----------------------------------
Summary: Dependency resolution fails when project version has a
suffix
Key: HIVE-30039
URL: https://issues.apache.org/jira/browse/HIVE-30039
Project: Hive
Issue Type: Bug
Reporter: Sercan Tekin
Assignee: Sercan Tekin
The issue is caused by a few places where internal Hive module dependencies use
{{${hive.version}}} instead of {{${project.version}}}.
This is similar to the issue addressed in
https://issues.apache.org/jira/browse/HIVE-29827, where {{${hive.version}}}
could differ from {{${project.version}}} when a custom project version or
suffix is used.
When Maven builds the reactor with a customized project version, for example
{{4.2.1-internal}}, the internal modules are built with that version:
{code:java}
[INFO] Reactor Summary for Hive 4.2.1-internal:
{code}
However, dependencies using {{${hive.version}}} may still resolve to the
original Hive version, such as {{4.2.1}}:
{code:java}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/hive/hive-iceberg-handler/4.2.1/hive-iceberg-handler-4.2.1.jar
{code}
Therefore, Maven cannot resolve the dependency from the reactor and attempts to
resolve the artifact from the configured Maven repositories instead.
Eventually, the build fails with:
{code:java}
Could not find artifact org.apache.hive:hive-iceberg-handler:jar:4.2.1 in
central (https://repo.maven.apache.org/maven2) -> [Help 1]
{code}
I will share a PR to align the dependency versioning and ensure that internal
Hive dependencies consistently use the project version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
