liveBook · Manning

Project object model

As explained in Spring in Action, Sixth Edition

A Maven project object model file that declares a project's metadata, dependencies, plugins, and build configuration.

A project object model is Maven’s XML build specification. The pom.xml declares project identity, inherits a parent POM, records Java settings, and organizes dependencies and build choices. section 1.2.2

Taco Cloud project

A generated Taco Cloud project uses pom.xml to identify the application, inherit spring-boot-starter-parent version 2.5.3, target Java 11, and list its dependencies. Maven Wrapper commands build, run, and test the project without requiring a separate Maven installation: ./mvnw package, ./mvnw spring-boot:run, and ./mvnw test. section 1.2.2

How Spring in Action, Sixth Edition covers it

How deep it goes
Explains the POM’s role and shows its generated XML, but postpones detailed configuration-property treatment.
Examples
Uses the Taco Cloud pom.xml, Maven Wrapper packaging, Spring Boot startup, and test commands as concrete artifacts.
What it assumes
Assumes a project generated with Spring Initializr and Maven selected, while introducing the POM’s purpose from the project structure.
What you can do after
Operate Maven Wrapper commands to package, run, and test a generated Spring Boot application.
How it connects
Connects Maven with Spring Initializr, Spring Boot, Maven Wrapper, Java, dependencies, and project structure.

Also explained in

Compare how 3 books explain project object model →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spring in Action, Sixth Edition. The section links point to the parts of the book it draws on.