Port the code generators to run as maven plugins and make them public

[david-at-aws]

All of the code in the service-specific modules is generated from JSON files that describe the resources for a service and how they relate together. Right now the code generators depend on some internal Amazon infrastructure, but we'd love to get them converted to run as Maven plugins so we can push them out to GitHub instead of just the code they generate. Comment here if that's something you'd like to see us prioritize!

[futurely]

It seems that you didn't use generic converters such as jsonschema2pojo. I'd like to know how did you implement the generator and how to validate that the json schema is consistent with the services API specification. Even if you don't convert the generator into Maven plugins, it's very helpful to share the existing code.

[david-at-aws]

Correct, it's not a generic POJO converter, since the generated resource objects aren't normal POJOs. I got about halfway through getting the code generators into a shareable form a while back before I got distracted by re:Invent - I'll see if I can get that finished up in the next couple weeks. Thanks for the reminder!

[futurely]

Among the many RESTful API specifications such as RAML, API-blueprint and WADL etc., Swagger is one of the most popular one that provides comprehensive tool sets including maven plugins and is one of the API specifications supported by the Microsoft Azure API management service (former APIphany). Swagger representes API specification as JSON as this project does.

The feature that is most relevant to this issue is the code generator. It can generate client, server and many more in most of the main stream languages.

[futurely]

APIphany must have been sold to Microsoft at a very good price considering the previous rounds of funding. Unfortunately, AWS doesn't have API management service yet.