stop the forked task after the generation of the OpenAPI spec #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the forked task
forkedSpringBootRun
is not automatically terminated after the generation of the OpenAPI specification.The problem description
I have a backend part of my application (REST interface), which is implemented with the aid of SpringBoot. The frontend part is just a Vue SPA, developed with the aid of Vite. The
springdoc-openapi-gradle-plugin
is used to generate the frontend code to communicate with the rest interface. So, the generation task is a dependency for the frontend development server. Currently, while the frontend development server is running the backend process is running too (because it is not automatically terminated), although the generation of the code is finished. In most cases it is not a problem, but if I need to start a backend in debug mode, it is impossible (because it is already started just normal for the code generation).So, the PR solves this problem by terminating the forked process after the generation is finished. It was already the case before switching to
gradle-execfork-plugin
, thus the PR should be treated as a regression fix.