You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
minor: (#173) remove incorrect Json2YamlTask and make the output format configurable (#175)
* minor: (#173) remove incorrect Json2YamlTask and make the output format configurable
* update docs
* add workaround for lazy task configuration of the `generateOpenApiDocs` task
---------
Signed-off-by: Clemens Grabmann <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+31-1Lines changed: 31 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -466,7 +466,37 @@ plugins {
466
466
}
467
467
```
468
468
469
-
The plugin has to be applied to a module that provides a Spring Boot application which the plugin will try to start using a custom Spring Boot run configuration.
469
+
The plugin has to be applied to a module that provides a Spring Boot application which the plugin will try to start using a custom Spring Boot run configuration.
470
+
This custom run configuration will be started in a dummy working directory to work around a issue currently present in the springdoc plugin. You can find more information [here](https://github.com/cloudflightio/autoconfigure-gradle-plugin/issues/171).
471
+
The dummy working directory is created with a task called `createDummyForkedSpringBootWorkingDir`. Various other tasks are automatically configured to depend on this, since they access the dummy directory for some reason.
472
+
473
+
<details>
474
+
<summary>If you run into some problems with the task, try adding it as a dependency to your task by adding the following.</summary>
The springdoc plugin is automatically configured to generate the open-api spec in `YAML` format. If you prefer the `JSON` format you can easily change that by using our extension:
// for some reason the springdoc plugin reads the values from the extension during task initialization and uses that as convention for the task properties,
54
+
// which results in some values being incorrect. Because of that we reconfigure the properties conventions to directly use the extension properties. And
55
+
// add conventions to the extension properties to the expected default values see: https://github.com/springdoc/springdoc-openapi-gradle-plugin/blob/master/src/main/kotlin/org/springdoc/openapi/gradle/plugin/OpenApiGeneratorTask.kt#L46
0 commit comments