Have spec file generation disabled when using server generation from spec file

[lucjross-favor]

Feature description

I'm trying to configure a build according to this guide: https://guides.micronaut.io/latest/micronaut-openapi-generator-server-gradle-java.html

But the build still tries to generate a spec out of the swagger annotations on the generated interfaces, and by default uses that generated spec for the views (swagger-ui). This doesn't make sense and the generated spec also loses detail present in the original spec because the process of spec -> annotated interfaces -> new spec is imperfect.

I think when server generation is used, spec generation should be disabled by default.

[melix]

I think this will require changes to Micronaut OpenAPI. Currently, OpenAPI Swagger generation is handled by the micronaut-openapi annotation processor, which is responsible for:

• generating a swagger definition file (this is what you're asking to disable)
• copying the Swagger UI resource files

There is a configuration property that you can set to disable OpenAPI annotation processing, the problem being that it will disable both, because both are guarded by the same test.

So in order to do this, we should probably have 2 different flags in Micronaut OpenAPI. If we do this, then this issue could be fixed by:

• having the source spec into src/main/resources/META-INF/swagger
• adding the micronaut.openapi.swagger.generation.enabled=false property to the application (assuming micronaut.openapi.swagger.generation.enabled is a new property).

/cc @altro3 wdyt?

[altro3]

@melix Hm...These are two unrelated modules. To disable the generation of a swagger file, you need to add the property: micronaut.openapi.enabled=false - this property does not affect the generator in any way (@lucjross-favor read https://micronaut-projects.github.io/micronaut-openapi/latest/guide/index.html).

There is no point in creating a new system property, because the settings are transferred to the generator from the plugin. And the settings for micronaut-openapi are passed through arguments to the annotation processor

[melix]

If you set micronaut.openapi.enabled=false then the swagger ui files are not copied to the application classpath. That's why I think we need to make the difference between generating the spec and copying the resources in the processor.

[altro3]

ok, I understood. Maybe need to move this issue to micronaut-openapi project. I'll do it when I have time