[ODLPARENT-275] Remove powermock declaration Created: 17/Oct/21 Updated: 14/Nov/21 Resolved: 14/Nov/21 |
|
| Status: | Resolved |
| Project: | odlparent |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | 10.0.0 |
| Type: | Task | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Powermock is a nigh-dead upstream, with a long history of technical issues w.r.t. integration with other tools – notably Mockito and JaCoCo. The Mockito issues seem to be solved at this point, but JaCoCo integration still does not work with on-the-fly instrumentation – as noted in There are four projects alive at this point using powermock:
Of these, transportpce manages powermock on its own (and is way behind at 2.0.2) and unimgr is still on odlparent-5 – hence they will not be negatively impacted by us removing the declaration. Lispflowmapping has only three tests which use Powermock and hence it is feasible to migrate. OVSDB has quite a few tests, but is also almost dead, so just declaring versions just as transportpce does should do the trick. Furthermore Mockito now has the ability to mock/spy static methods and final classes, which should work nicely as it is based on ByteBuddy. |