Avoid using org.hamcrest due to module issues#1596
Merged
cheenamalhotra merged 1 commit intodevfrom Jul 13, 2021
Merged
Conversation
Contributor
|
/azp run Microsoft.mssql-jdbc.macOS |
|
No pipelines are associated with this pull request. |
cheenamalhotra
force-pushed
the
hamcrest
branch
2 times, most recently
from
c32ac37 to
0a1b802
Compare
karinazhou
approved these changes
Jun 18, 2021
Contributor
|
/azp run Microsoft.mssql-jdbc.windows |
|
No pipelines are associated with this pull request. |
lilgreenbird
approved these changes
Jul 13, 2021
VeryVerySpicy
approved these changes
Jul 13, 2021
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
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.
org.hamcrest classes fails to resolve to module and below module conflict each other:
Steps to reproduce:
If it's not absolutely needed, tests can avoid using these Junit APIs as standard alternatives are available.