Maven BOM (Bill of Materials)

Q: Maven BOM (Bill of Materials)

A Maven BOM is a POM—usually imported into `dependencyManagement` with type `pom` and scope `import`—that supplies a coordinated set of dependency versions. It does not add those libraries by itself and cannot guarantee compatibility; consumers still declare the dependencies they use and rely on the BOM maintainer's tested recommendations.

Beginner·4 min read·

AmazonGoogleMicrosoft

Fast recall

Quick revision

Core answer

A Maven BOM is a POM—usually imported into dependencyManagement with type pom and scope import—that supplies a coordinated set of dependency versions. It does not add those libraries by itself and cannot guarantee compatibility; consumers still declare the dependencies they use and rely on the BOM maintainer's tested recommendations.

Interview Answer4 min

A BOM, or Bill of Materials, is a special Maven POM file that contains a curated set of dependency versions that are known to work together. It's not a library that provides classes—it's more like a version lookup table. When you import a BOM, you're essentially saying "I trust this organization to tell me which versions are compatible." The most common example is Spring Boot. Spring Boot maintains a BOM called spring-boot-dependencies that lists tested versions for hundreds of libraries: Spring Framework, Jackson, Hibernate, Tomcat, and so on. Instead of you manually figuring out that Spring six point oh point eleven works with Jackson two point fifteen point three, you just import the Spring Boot BOM. Here's how it works. In your pom.xml, you have a dependencyManagement section—not the regular dependencies section. Inside dependencyManagement, you add the BOM as a dependency with type pom and scope import. This tells Maven to pull in all the version definitions from that BOM. Then, down in your regular dependencies section, you add the libraries you actually want, but you leave out the version tags. Maven looks up the version in the BOM you imported. For example, you'd add spring-boot-starter-web without a version, and Maven uses whatever version the BOM says, which is three point two point oh in this case. The beauty is you don't have to worry about compatibility—Spring Boot already tested all those versions together. One common mistake is putting the BOM in the regular dependencies section instead of dependencyManagement. That won't work because scope import only works in dependencyManagement. Another mistake is thinking the BOM adds dependencies to your project. It doesn't. You still have to explicitly list each dependency you want—the BOM just manages the versions. Most Spring Boot developers actually use a BOM without realizing it. When you extend spring-boot-starter-parent in your POM, that parent is essentially a BOM plus some Maven plugin configuration.

Interview-ready guide

Interview answer

A BOM, or Bill of Materials, is a special Maven POM file that contains a curated set of dependency versions that are known to work together.

It's not a library that provides classes—it's more like a version lookup table. " The most common example is Spring Boot. Spring Boot maintains a BOM called spring-boot-dependencies that lists tested versions for hundreds of libraries: Spring Framework, Jackson, Hibernate, Tomcat, and so on.

Instead of you manually figuring out that Spring six point oh point eleven works with Jackson two point fifteen point three, you just import the Spring Boot BOM. Here's how it works. xml, you have a dependencyManagement section—not the regular dependencies section.

Inside dependencyManagement, you add the BOM as a dependency with type pom and scope import. This tells Maven to pull in all the version definitions from that BOM. Then, down in your regular dependencies section, you add the libraries you actually want, but you leave out the version tags.

Maven looks up the version in the BOM you imported.

For example, you'd add spring-boot-starter-web without a version, and Maven uses whatever version the BOM says, which is three point two point oh in this case. The beauty is you don't have to worry about compatibility—Spring Boot already tested all those versions together. One common mistake is putting the BOM in the regular dependencies section instead of dependencyManagement.

That won't work because scope import only works in dependencyManagement. Another mistake is thinking the BOM adds dependencies to your project. It doesn't.

You still have to explicitly list each dependency you want—the BOM just manages the versions. Most Spring Boot developers actually use a BOM without realizing it. When you extend spring-boot-starter-parent in your POM, that parent is essentially a BOM plus some Maven plugin configuration.

03 · Deep dive