Troubleshooting
Checks the configuration and support code shapes in order when there are no generated files or when route/type is missing.
Verification order
• Check if @Profile("local") is included in the actual execution profile.
• Ensure that no exceptions occur in the local console for runner.start().
• Verify that rootPath, routerPackage, entityPackage, and handlerOutputDir are in the correct locations after dot/slash conversion.
• Check if the generated source directory is included in the IDE and build tool source set.
• Add external common module types to decompile jar class or source classpath.
• Ensure that RouterFunction is in a fluent route/nest and handler method reference form.
Dot path and slash path
Config normalizes . to / in multiple path inputs. While package strings and filesystem paths can be mixed, you need to check the difference between configurations that include the full output path like src.main.java.com.example... and those that only include the com.example... package.
Infinite regeneration
The Swagger writer only writes the file when the content changes. If regeneration occurs repeatedly, check if the output file is included in the watchDirectory, and whether a formatter or other watcher is continuously modifying the generated source.