[jira] [Work logged] (HIVE-26331) Use maven-surefire-plugin version consistently in standalone-metastore modules

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-26331?focusedWorklogId=781617&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-781617 ]

ASF GitHub Bot logged work on HIVE-26331:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Jun/22 12:04
            Start Date: 15/Jun/22 12:04
    Worklog Time Spent: 10m 
      Work Description: zabetak opened a new pull request, #3374:
URL: https://github.com/apache/hive/pull/3374

   ### What changes were proposed in this pull request?
   Move maven-surefire-plugin management to common parent module (standalone-metastore)
   
   ### Why are the changes needed?
   1. Use the same plugin version (3.0.0-M4) in all modules
   2. Simplify dependency management
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   ### How was this patch tested?
   `mvn clean install -DskipTests -Pitests | grep "surefire-plugin" ` and check manually that the same version is used in all modules




Issue Time Tracking
-------------------

            Worklog Id:     (was: 781617)
    Remaining Estimate: 0h
            Time Spent: 10m

> Use maven-surefire-plugin version consistently in standalone-metastore modules
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-26331
>                 URL: https://issues.apache.org/jira/browse/HIVE-26331
>             Project: Hive
>          Issue Type: Task
>          Components: Standalone Metastore, Testing Infrastructure
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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+ 
> {noformat}
> [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 ---
> {noformat}
> The goal of this JIRA is to ensure we use the same version consistently in all modules.
> +Expected+
> {noformat}
> [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 ---
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)