Many bindings which communicate with an external web API keep the representation of the API as (possibly hand-written) DTOs in the main source tree. For example my pushbullet and sensebox bindings, but there are many more of them. On the other hand, there are usually schemata available for these APIs, often offered by the external service.
I’d like to generate those classes (at least on my bindings) so I keep just the schema in src/main/resources/whatever, either http://www.jsonschema2pojo.org/ or http://www.mojohaus.org/jaxb2-maven-plugin/ , depending on which language the schema is offered.
Is this acceptable for the development community? I know @Kai wants developers to be able to be able to start working immediately after cloning, but I having developers do work that is much easier done by the build system sounds strange to me. Also, this would reduce the lines of code to review, which would make @David_Graeff happier I guess