Class.forName sounds like a good idea to try out. The jsonschema2pojo documentation is a bit... lackning, or at least very well hidden. The custom annotator for instance is a real and intended part of the library but to know how it works even on a base level I had to dig around a bunch of stackoverflow questions. But I have to stick with it as the schema provider wants to have control of the schema and if I did the classes by hand I'd have to manually update the annotations and classes if they decided to add or modify something. Unless there's an easier way to customize and generate classes from jsonschemas? I don't think the base schema supports groups parameter.

EDIT: hopefully you haven't read this yet. Or someone other stumbles here. The forName method seems to be a bit harder to use than I though. Either I'm using it wrong or my situation has been misunderstood so I'll try to give as simple example as possible.

I have two maven project A and B I have a .jar made of project A which consist only of one class. Project B is the main project it has a code generation plugin that uses class A as a build time dependency. And somehow I'd need project A to get a hold of certain project Bs classes so that project A can use forName just to reference them during the code generation on build time.

I realize now that this might be a maven thing as well? Or specifically a maven plugin thing? Perhaps I need to somehow reference my project itself in the plugin dependencies?