[ https://issues.apache.org/jira/browse/KAFKA-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440831#comment-17440831 ]
Liam Clarke-Hutchinson edited comment on KAFKA-12220 at 11/9/21, 12:42 AM: --------------------------------------------------------------------------- Hi [~chia7712] and [~ijuma] - I hit Powermock/Easymock issues (Java 16+ breaks Powermock) in org.apache.kafka.connect.runtime.WorkerTest.java and it's a fairly large file. Firstly, I want to check no-one else is working in this area, and secondly, seeing as WorkerTest is so large, would it be okay to submit a PR for just that one file? Lastly, if all of the above is okay, should I add as a subtask to this issue or to KAFKA-7438? was (Author: JIRAUSER279886): Hi [~chia7712] and [~ijuma] - I hit Powermock/Easymock issues (JRE >16+) in org.apache.kafka.connect.runtime.WorkerTest.java and it's a fairly large file. Firstly, I want to check no-one else is working in this area, and secondly, seeing as WorkerTest is so large, would it be okay to submit a PR for just that one file? Lastly, if all of the above is okay, should I add as a subtask to this issue or to KAFKA-7438? > Replace PowerMock by Mockito > ---------------------------- > > Key: KAFKA-12220 > URL: https://issues.apache.org/jira/browse/KAFKA-12220 > Project: Kafka > Issue Type: Improvement > Reporter: Chia-Ping Tsai > Assignee: Chia-Ping Tsai > Priority: Major > > We are migrating project from junit 4 to junit 5 (KAFKA-7339). PowerMock, > however, does not support junit 5 totally > (https://github.com/powermock/powermock/issues/830). Hence, we ought to > replace PowerMock by Mockito before migrating to junit 5 since rewriting all > tests which are depending on PowerMock can bring a bunch of changes. -- This message was sent by Atlassian Jira (v8.20.1#820001)