Troubleshooting

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.

import com.byeolnaerim.watch.route.HandlerGenerator;

var handlerConfig = HandlerGenerator.Config.builder()
    .rootPath("src/main/java")
    .routerPackage("com.example.web.router")
    .handlerPackage("com.example.web.handler")
    .handlerOutputDir("src/main/java/com/example/web/handler")
    .build();

System.out.println(handlerConfig.routerDir());
// src/main/java/com/example/web/router/

Run from the project root and check that the printed routerDir contains the router source. Including src/main/java in routerPackage duplicates the path. Pass this configuration to the runner's handlerConfig and run with the local profile from Quick Start. handlerPackage is the Java package name; handlerOutputDir is the actual output directory.

test -d src/main/java/com/example/web/router
find src/main/java/com/example/web/handler -name '*.java'
# Quick Start swaggerOutputFile:
test -s src/main/resources/static/swagger.json

If the paths are correct but output is missing, start with the first exception from runner.start(). Reproduce with one minimal route using a handler::method reference, inspect the generated files, then add your existing routes. A swagger.json file alone does not establish correctness: check the request path and HTTP method in paths against the actual response contract.

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.