Github user smoyer64 commented on the issue:
https://github.com/apache/commons-lang/pull/353
@kinow
> Alternatively, you can update the PR with some base work that you think
might be useful for the next iterations. Up to you
If the intention is to use the conversion as an opportunity to review all
the test classes, then completing the automatic conversion is probably a bad
idea. Once the tests are running again, nobody's going to look at them right?
Most of the changes made by the converter were boilerplate ... greater than 80%
of the test classes only had changes to their imports. I could create a branch
that was nothing more than the conversion if you're interested and people could
pick off a class, optimize/update it and submit a single class as a PR.
The conversion tool needs a little work but it's also capable of converting
a single file at a time. Or I can drop the whole idea of automation.
---