Potential Refactoring Estimate

Summary
I have identified a few classes with refactoring potential along with its estimated time to refactor, specifically CodeGenMojo.java. The estimated time is based on historical commits containing refactoring and the complexity of the involved classes. The class was refactored once on Feb 9, 2020 along with other classes in commit 4602596df2dacab0b4fd99458e213ff4cdd2b182. Given the duration of the last refactoring, could it be possible to improve this class further? I am probably not qualified and experienced enough to point out the exact code needs to be refactored, given my limited knowledge of the project and codebase.

Urgency
Low priority. For maintenance of code in the long run.

Hi,
I am currently doing some research on Estimating Time Taken for Software Refactoring. Openapi-generator is one of my case studies being a highly popular project. Would appreciate your kind feedback on the appropriateness of the estimated time to refactor.
I am specifically looking at potential for refactoring, such as breaking functions that are too long into shorter functions, or to remove code duplication. Would you agree that there could be some modification to the code to make it better in the listed classes? And if so, is the estimated time appropriate to carry out the improvement? I will be grateful for any help you can provide.

1. CodeGenMojo.java - 4.5 hours
2. CodegenConfigurator.java - 3 hours
3. CodegenConfiguratorUtils.java - 5 hours

Thank you.

Regards,
Alvin

Start by reading CodeGenMojo.java, CodegenConfigurator.java, and CodegenConfiguratorUtils.java, then compare them with historical refactoring commit 4602596df2dacab0b4fd99458e213ff4cdd2b182. Before making changes, establish a concrete refactoring scope and verify that the proposed improvements have clear validation criteria.