pet-store | React Crash Course Pet Store '' Example | Frontend Framework library

I came across your question as I was trying to cope with OAS 3.0 and therefore using the mentioned openapi-generator-maven-plugin. Meanwhile I got it to generate exactly what you are describing.

I would suggest dealing with this by

1. generating your model and API classes to a separate package from your code and
2. configuring Spring's @ComponentScan annotation to not include the generated classes (either with the basePackages property alone or combining it with the explicit excludeFilters property).

And yes, modifying generated classes is bad. I'd just use them as a starting point for creating your actual controllers.

Amendment: After configuring the code generation in various ways I found the best solution to have only the API (interfaces) being created. This way I can implement my controller without having another implementation interfering with it.

To achieve this my plugin config now looks like this (using the configOptions/interfaceOnly option):