linghengqian opened a new issue, #19845: URL: https://github.com/apache/shardingsphere/issues/19845
## Feature Request **For English only**, other languages will not accept. Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot make decision by current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Is your feature request related to a problem? Yes, refer to https://github.com/apache/shardingsphere/pull/15296 . ### Describe the feature you would like. - According to https://github.com/junit-team/junit4/pull/1150, Hamcrest related APIs are deprecated in Junit 4.13.x. Meanwhile, according to the discussion at https://github.com/junit-team/junit4/issues/1741, Junit4 is likely to completely remove the Hamcrest dependency in the next major version, which means like `org.junit.Assert.assertThat` will be removed. - I think the recommendation in the Code of Conduct to replace `org.junit.Assert.assertThat` with `org.hamcrest.MatcherAssert.assertThat` in `hamcrest 1.3` might be a good future-proof option. -- 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]
