Generated Modules

Fixed Modules

These modules are always generated regardless of input.

common-domain

Domain classes shared across all other modules. No dependencies on other generated modules.

Package: {base.package}.common.domain

common-testing

Shared test utilities. Has no test-scope Java packages.

Package: {base.package}.common.testing
Depends on: common-domain

service or service-{name}

Business logic for a service area (see the serviceAreas prompt).

Package: {base.package}.service or {base.package}.service.{name}
Depends on: common-domain

app

Application assembly — produces the runnable artifact (e.g. Spring Boot über-jar).

Package: {base.package}.app
Depends on: all non-test modules (common-domain, all domain and integration modules, all service modules, all presentation modules)

acceptance-tests

Functional acceptance tests that exercise the application from the outside. Has no main-scope Java packages.

Package: {base.package}.at
Depends on: app, common-domain, all domain-{type}-{name} integration domain modules, all domain-{type} presentation domain modules
Plugin: maven-failsafe-plugin (integration-test + verify goals)

Integration Modules

Generated per type:name pair in the integrations prompt. The database type is abbreviated to db in all names.

domain-{type}-{name}

Domain classes for a specific integration (e.g. domain-db-users, domain-rest-orders).

Package: {base.package}.domain.{type}.{name}
Depends on: common-domain

integration-{type}-{name}

Integration implementation classes — DAOs, Spring Data JPA repositories, REST clients, etc. (e.g. integration-db-users, integration-rest-orders).

Package: {base.package}.integration.{type}.{name}
Depends on: common-domain, domain-{type}-{name}
Plugin: maven-failsafe-plugin (integration-test + verify goals)

Presentation Modules

Generated per type in the presentationTypes prompt.

domain-{type}

Domain classes for a presentation tier (e.g. domain-rest, domain-graphql).

Package: {base.package}.domain.{type}
Depends on: common-domain

presentation-{type}

Request-handling classes — controllers, resolvers, etc. (e.g. presentation-rest, presentation-graphql).

Package: {base.package}.presentation.{type}
Depends on: common-domain, domain-{type}

Parent POM

parent/pom.xml is the aggregator and BOM for all sibling modules. There is no pom.xml at the project root — parent/ is a sibling of all other modules.

It contains:

• <packaging>pom</packaging>
• <modules> — all sibling modules referenced as ../module relative paths, sorted alphabetically
• <dependencyManagement> — all modules pinned to ${project.version}, sorted alphabetically by artifactId
• Common properties: Java 21 via maven.compiler.release; UTF-8 source encoding
• <pluginManagement> — pinned versions for maven-compiler-plugin, maven-failsafe-plugin, maven-jar-plugin (with skipIfEmpty=true), and maven-surefire-plugin

To build a generated project:

cd my-service/parent
mvn verify

Use mvn install instead if other local projects need to consume the generated modules from your local Maven repository.

Package Reference

All type and name segments in package names are lowercased.