HIVE-27592: Remove mockito from root pom.xml #4576
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asf-ci-hive
added
tests pending
tests failed
and removed
tests pending
tests failed
labels
|
Kudos, SonarCloud Quality Gate passed!
|
Contributor
Author
|
Note: It helps to finish my other PR about PowerMock here: #3798 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change removes Mockito dependency from the root pom.xml to be able to upgrade mockito on a module bases and it enables removing PowerMock.
Upstream conversation in the ticket: https://issues.apache.org/jira/browse/HIVE-27592
What changes were proposed in this pull request?
Remove Mockito and PowerMock from root pom.xml and define those dependencies in the projects that are using them.
Why are the changes needed?
To be able to remove PowerMock module-by-module.
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?
By running precommit tests.