> Considering everything, I see only one options: > > Write a tool that "clones" the project and strips all the methods that we > don't want. So you'd run the tool and you'd get a *new* Maven project which > contains only the code that you want. Should be pretty simple to do with the > AST parser that I posted about since you'd just have to copy any non-java > file and filter the methods by annotations and then create a new source file > with toString() (more or less).
That won't work for two reasons: 1. jOOQ relies on the @Override annotation to declare that an implementation method implements an interface method 2. jOOQ uses jOOQ API internally from the public API. Removing method declarations from the public API will (probably) lead to compilation errors > - Create one interface per database and implement that or use a clever proxy > handler -> doesn't work because of the static methods. ...and because I won't spend time maintaining such a solution. > - Strip the code inline -> That would either confuse Eclipse (you can't edit > the original source code anymore) or Maven (generating source code into the > folder src/*/java isn't defined behavior). I'm not sure what that means.
