Lodsve Maven Archetype

Lodsve Boot scaffolding prepared for Maven projects, covering basic Web, MyBatis, Nacos and RPC projects.

Project positioning

lodsve-maven-archetype encapsulates Lodsve Boot engineering convention as Maven Archetype. Generate POM, Java files and configurations through project coordinates, package names, Boot versions and other parameters to reduce the work of manually building the directory structure.

Six template modules

TemplatePurposeInstructions for use
lodsve-archetype-quickstartBasic Web Engineering and Common LayersQuickstart
lodsve-archetype-mybatisData source, DAO, PO and Mapper examplesMyBatis
lodsve-archetype-nacosBasic Web Project and Nacos Configuration Center ExampleNacos
lodsve-archetype-rpc-apiShared Feign interface, DTO and path constantsRPC API
lodsve-archetype-rpc-serverServer-side implementation of API interfaceRPC Server
lodsve-archetype-rpc-clientClient project that calls shared APIRPC Client

All templates use groupId com.lodsve.archetype. For the collaboration process of the three RPC modules, see RPC Engineering Guide.

version boundaries

The document structure and parameters are based on the warehouse d1450a5, and the revision of its root POM is 1.0.4-SNAPSHOT. Maven Central can find the 1.0.3 releases of Quickstart, MyBatis, and Nacos; for the RPC module, please click RPC Guide Installing from source, you cannot assume that they are also released with the same version.

archetypeVersion selects the template version, bootVersion selects the Lodsve Boot version that the application depends on, and version is the version of the new business project. The three are not interchangeable. The current template is for Lodsve Boot 1.0.4-SNAPSHOT / Spring Boot 4.1.2; the generated project uses Jakarta API and Springdoc OpenAPI 3, and is no longer compatible with Boot 2/3’s javax.* and Springfox annotations.

Source code basis

Chinese README · Source revision d1450a5 · Report an issue

The README in each template currently only retains the project name placeholder. This chapter also refers to the respective archetype-metadata.xml, POM, Java files and YAML configurations.

Read the docs

Architecture diagram