Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
Due to some problems in the pom.xml files inside the standalone-metastore modules we end up using different maven-surefire-plugin versions.
Most of the modules use 3.0.0-M4, which is the expected one, while
the hive-standalone-metastore-common uses the older 2.22.0 version.
Actual
[INFO] --- maven-surefire-plugin:2.22.0:test (default-test) @ hive-standalone-metastore-common --- [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ hive-metastore --- [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ hive-standalone-metastore-server --- [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ metastore-tools-common --- [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ hive-metastore-benchmarks ---
The goal of this JIRA is to ensure we use the same version consistently in all modules.
Expected
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ hive-standalone-metastore-common --- [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ hive-metastore --- [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ hive-standalone-metastore-server --- [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ metastore-tools-common --- [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ hive-metastore-benchmarks ---
Attachments
Issue Links
- is related to
-
HIVE-26063 Upgrade Apache parent POM to version 25
-
- Open
-
- links to
