Project Builder

Use a guided workflow to choose Spring Boot versions, project metadata and dependencies for a standardized project structure.

Project builder capabilities

Rapidly generate Spring Boot project structures via a visual wizard, supporting dependency selection and version management.

  • Intuitive Configuration Wizard: Provides a graphical interface to easily configure basic information such as project metadata, package name, and Java version.
  • Rich Dependencies: Built-in common Spring Boot Starter dependencies, supporting on-demand selection and automatic version compatibility handling.

Step-by-step guide

  1. Open the Project Builder and choose build tool (Maven/Gradle) and language.
  2. Fill in groupId/artifactId/package and choose Java & Spring Boot versions.
  3. Select dependencies (Starters) needed by your business scenario.
  4. Generate the project and import it into IntelliJ IDEA.

Best practices

  • Keep artifactId short and stable; avoid renaming later.
  • Pick the Java version based on your runtime and CI/CD environment.
  • Add only necessary dependencies first; grow gradually to reduce complexity.
  • Use consistent naming conventions across services to improve onboarding.

FAQ

Q: Which Spring Boot version should I choose?

Prefer the latest stable line supported by your production environment. If your company has a standard BOM, align with it.

Q: I selected dependencies but the project fails to build.

Check JDK version, Maven/Gradle mirror settings, and dependency conflicts. Starting from a minimal set and adding dependencies one by one helps locate the problematic one.

Project types it fits

  • Spring Boot Web APIs, admin backends, scheduled jobs, and microservice modules.
  • Team projects that need consistent groupId, artifactId, and package naming.
  • Prototype projects used to validate Spring Boot Starter combinations and Java compatibility.
  • Local IntelliJ IDEA workflows that keep initialization, dependency selection, and import in one place.