Spring Boot Project Generator

Problem Addressed

When starting a new Spring Boot service, engineers often repeat the same setup work: creating the directory layout, adding configuration, defining a unified response wrapper, handling exceptions, and wiring logging or caching. springboot-generator targets this repetitive scaffolding by generating a standard Spring Boot structure directly in the current working directory, including pom.xml, application.yml, the bootstrap class, exception handlers, and configuration classes, without creating an extra subdirectory.

Core Capabilities

• Parameter confirmation: asks for groupId, artifactId, version, springBootVersion, packageName, and author; groupId is required, while artifactId defaults to the current directory name.
• Version mapping: selects compatible MyBatis Plus, Knife4j, and MySQL Connector versions based on the Spring Boot version.
• Unified responses and exceptions: generates Result, ResultCode, BizException, and GlobalExceptionHandler, with JSR-303 validation support.
• Context and pagination: provides UserContext, UserContextInterceptor, and PageResult for request-scoped data and paginated queries.
• Logging and caching: includes the ShowLog annotation, ShowLogHandler aspect, CacheDataAnnotation, and caching AOP, with Redis serialization configured.
• API documentation: integrates Knife4j, which can be disabled with knife4j.enable: false.

Boundaries and Notes

• The generated project targets JDK 17, so the local toolchain must be compatible.
• It assumes the current directory is already prepared, because output is written directly there.
• Database settings in application.yml still need to be updated after generation.
• Redis-related dependencies can be removed if the service does not use Redis.
• A standard package layout such as com.company.project is recommended to avoid naming conflicts during later refactoring.