sercanCyberVision opened a new pull request, #6775:
URL: https://github.com/apache/hive/pull/6775
**PROBLEM**
When Maven builds the reactor with a customized project version, for example
`4.2.1-internal`, the internal modules are built with that version:
```
[INFO] Reactor Summary for Hive 4.2.1-internal:
```
However, dependencies using `${hive.version}` may still resolve to the
original Hive version, such as `4.2.1`:
```
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
```
**ROOT CAUSE**
1. Unlike the main POM, which defines
`<hive.version>${project.version}</hive.version>`, the standalone-metastore POM
has the Hive version hardcoded as `<hive.version>4.2.1</hive.version>`.
2. In the standalone-metastore sub-modules, there are a few places where
internal Hive module dependencies use `${hive.version}` instead of
`${project.version}`.
**SOLUTION**
1. Changed the `hive.version` property in standalone-metastore to make it
consistent with the main POM.
2. Changed the internal dependency versions from `${hive.version}` to
`${project.version}`.
**CHECKS**
With the modified project version, I ran:
```
mvn dependency:tree -Dincludes=org.apache.hive:*
```
and verified that all internal Hive dependencies use the project version,
ensuring that the corresponding artifacts are resolved from the Maven reactor.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
