Maker VS JavaParser

If you want an alternative to ASM, try Cojen/Maker, which is designed to be much easier to use than any of the other class writing APIs, including the one proposed by JEP-8280389. Here's a comparison.

That's a lot right arrow operators just to implement a simple Hello World program (5). I can't even begin to imagine how difficult it might be to generate anything more interesting than this. Here's a comparison against a classfile API which is designed to be easy to use: https://github.com/cojen/Maker/wiki/JEP-8280389

For the code generation phase, it might be easier to bypass emitting a text-based assembly format and just use the ASM library directly. If you want something easier, I wrote a code generation library specifically for that purpose: https://github.com/cojen/Maker It also includes an example "Mini-C" language compiler.

As I have never seen generic constructors before I wanted to know how "real-world" code uses them. So I wrote a program that parses the Java files in the JDK source code. It uses the JavaParser open-source library. Since its README file mentions Java 15, I ran the program on tag jdk-15+36 of the JDK source code.

GitHub released a pretty good java parser that I think is is related to this work https://github.com/javaparser/javaparser

I'm also using that parser using for a side project where developers can cross link their source code and host them statically: https://github.com/josephmate/OdinCodeBrowser#readme

JavaParser

So after taking a deeper look into the docs I've seen that analysis is done via https://github.com/javaparser/javaparser/ lib which has currently only support up to JDK14 (not JDK15, JDK16 nor JDK17...maybe JDK18)...Unfortunately I have not found a full working example for a Java build ...can you give a link?

Depending on the type of refactorings needed, you may be able to use something like Java parser to read the code, refractor it, and write it out again.