If other components are considering a switch to JUnit 5, we've got a reasonable converter at https://github.com/junit-pioneer/convert-junit4-to-junit5. For many projects it seems to convert about 90-95% of the code - there are some of the missing edge cases listed in the issue tracker.
Steve ________________________________ From: Emmanuel Lecharny (JIRA) <[email protected]> Sent: Monday, May 6, 2019 12:51 PM To: [email protected] Subject: [jira] [Commented] (DIRAPI-333) Switch to Junit 5 [ https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FDIRAPI-333%3Fpage%3Dcom.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel%26focusedCommentId%3D16833996%23comment-16833996&data=02%7C01%7Cswm16%40psu.edu%7Caad77a065b924a03991208d6d2430bd3%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636927582738767883&sdata=%2FXYAKMOb2qhn1BImGawVbUhPSOBUQJTgYWr5KEKVDVc%3D&reserved=0 ] Emmanuel Lecharny commented on DIRAPI-333: ------------------------------------------ And fixed with {{a6d42bdeca875f78e676541bb3f1a8780e4fc978}}. We had random test failures, which were due to the hierarchy of classes ({{AbstractCodecServiceTest}} which was extended by the tests, and it was initializing the {{LdapApiService}} instance, but it seems that {{@BeforeAll}} or {{@BeforeEach}} kind of bypass the parent constructor) > Switch to Junit 5 > ----------------- > > Key: DIRAPI-333 > URL: > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FDIRAPI-333&data=02%7C01%7Cswm16%40psu.edu%7Caad77a065b924a03991208d6d2430bd3%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636927582738767883&sdata=utKunF64A4yI3llragtUo3fONA2i2VrKdfUr2K%2BAr7I%3D&reserved=0 > Project: Directory Client API > Issue Type: Dependency upgrade > Affects Versions: 2.0.0.AM2 > Reporter: Maxim Solodovnik > Priority: Major > Fix For: 2.0.0.AM3 > > > commons-lang and commons-collections need to be updated to most recent > versions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
