POM.xml and dependencies in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the pom.xml file in a Spring Boot project?

The pom.xml file is used to manage the project configuration, including dependencies, build settings, and plugins. It tells Maven how to build and package the project.

beginner

How do you add a dependency in pom.xml?

You add a dependency inside the <dependencies> section using the <dependency> tag with <groupId>, <artifactId>, and <version> elements.

beginner

What happens when you add a new dependency in pom.xml and run your Spring Boot project?

Maven downloads the required library and its dependencies automatically, making them available to your project without manual setup.

intermediate

What is the role of spring-boot-starter dependencies in pom.xml?

spring-boot-starter dependencies provide a convenient way to include a set of related libraries for common tasks like web development, data access, or security.

intermediate

Why is it important to manage dependency versions in pom.xml?

Managing versions ensures compatibility and stability. It prevents conflicts between libraries and helps maintain consistent builds.

Where do you specify the dependencies in a Maven project?

A Inside the <dependencies> tag in pom.xml

B In the application.properties file

C In the src/main/java folder

D In the README.md file

Dependencies are declared inside the section of the pom.xml file.

What does the <groupId> element represent in a dependency?

A The build tool used

B The version number of the dependency

C The unique identifier of the project group or organization

D The name of the Java class

identifies the organization or group that provides the dependency.

Which of these is a common Spring Boot starter dependency for web applications?

A spring-boot-starter-web

B spring-boot-starter-data-jpa

C spring-boot-starter-security

D spring-boot-starter-test

spring-boot-starter-web includes libraries needed to build web applications.

What tool uses the pom.xml file to manage dependencies?

A Ant

B Maven

C Gradle

D NPM

Maven uses pom.xml to manage project dependencies and build lifecycle.

If you forget to add a required dependency in pom.xml, what will happen?

A Your project will run without any issues

B Maven will automatically add it for you

C The dependency will be downloaded but not used

D Your project will fail to compile or run due to missing classes

Missing dependencies cause compile or runtime errors because required classes are not found.

Explain the structure of a dependency entry in pom.xml and why each part is important.

Think about how Maven identifies and downloads the library.

Describe how Spring Boot starters simplify dependency management in pom.xml.

Consider how starters bundle related dependencies together.

Practice

1. What is the main purpose of the pom.xml file in a Spring Boot project?

easy

A. To configure the web server settings

B. To manage project configuration and dependencies

C. To store database records

D. To write Java code for the application

Solution

1. Step 1: Understand the role of pom.xml

   The pom.xml file is used to organize project settings and list needed libraries.

2. Step 2: Identify what pom.xml does not do

   It does not contain Java code, database data, or server settings directly.

3. Final Answer:

   To manage project configuration and dependencies -> Option B

4. Quick Check:

   Project setup = Manage dependencies [OK]

Hint: Think of pom.xml as your project's shopping list [OK]

Common Mistakes:

• Confusing pom.xml with Java source files
• Thinking it stores runtime data
• Assuming it configures server directly

2. Which of the following is the correct way to add the Spring Boot starter web dependency in pom.xml?

easy

A. \n org.springframework.boot\n spring-boot-starter-web\n

B. \n springframework.boot\n spring-web-starter\n

C. \n org.springframework\n boot-starter-web\n

D. \n org.boot.spring\n starter-web\n

Solution

1. Step 1: Check the correct groupId and artifactId for Spring Boot web starter

   The official groupId is org.springframework.boot and artifactId is spring-boot-starter-web.

2. Step 2: Compare options to official naming

   Only \n org.springframework.boot\n spring-boot-starter-web\n matches the exact correct groupId and artifactId.

3. Final Answer:

   Correct dependency XML with org.springframework.boot and spring-boot-starter-web -> Option A

4. Quick Check:

   Correct groupId/artifactId = \n org.springframework.boot\n spring-boot-starter-web\n [OK]

Hint: Remember exact spelling of groupId and artifactId [OK]

Common Mistakes:

• Swapping groupId and artifactId
• Misspelling 'spring-boot-starter-web'
• Using wrong groupId like 'springframework.boot'

3. Given this pom.xml snippet, what will happen when you run mvn clean install?

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>

medium

A. Only the JPA API will be included, no implementation

B. The project will fail because version is missing

C. The project will include JPA support and related libraries automatically

D. The dependency will be ignored without a scope tag

Solution

1. Step 1: Understand Spring Boot starter dependencies

   Spring Boot starters manage versions internally, so explicit version is not needed if parent is set.

2. Step 2: Recognize what spring-boot-starter-data-jpa provides

   It includes JPA API and an implementation like Hibernate automatically.

3. Final Answer:

   The project will include JPA support and related libraries automatically -> Option C

4. Quick Check:

   Spring Boot starters handle versions and implementations [OK]

Hint: Spring Boot starters bundle needed libs and versions [OK]

Common Mistakes:

• Thinking version tag is always required
• Assuming only API without implementation
• Believing scope tag is mandatory for dependencies

4. You added this dependency to your pom.xml but get a build error:

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-web</artifactId>
  <version>2.3.0.RELEASE</version>
</dependency>

What is the likely cause?

medium

A. Incorrect groupId spelling

B. Missing scope tag causes build failure

C. Dependency must be in build section, not dependencies

D. Version conflicts because Spring Boot parent manages versions

Solution

1. Step 1: Understand Spring Boot parent version management

   Spring Boot starter parent manages dependency versions automatically.

2. Step 2: Identify problem with manually specifying version

   Manually adding version can cause conflicts and build errors.

3. Final Answer:

   Version conflicts because Spring Boot parent manages versions -> Option D

4. Quick Check:

   Let parent manage versions to avoid conflicts [OK]

Hint: Avoid manual versions if using Spring Boot starter parent [OK]

Common Mistakes:

• Adding version manually when parent manages it
• Thinking scope is required for starters
• Misplacing dependencies outside dependencies

5. You want to add a custom library that is not in Maven Central to your Spring Boot project. Which is the best way to include it in your pom.xml?

hard

A. Upload the library to a remote repository and add its repository URL and dependency with version

B. Install the library in your local Maven repository and add a dependency without version

C. Add the library jar directly to your project and reference it in pom.xml with system scope

D. Add the dependency with a fake groupId and artifactId to trick Maven

Solution

1. Step 1: Understand how Maven resolves dependencies

   Maven downloads dependencies from repositories defined in pom.xml or local repo.

2. Step 2: Identify best practice for custom libraries

   Uploading to a remote repository and adding its URL in pom.xml is clean and maintainable.

3. Step 3: Why other options are less ideal

   Local install requires manual setup; system scope is discouraged; fake IDs cause errors.

4. Final Answer:

   Upload the library to a remote repository and add its repository URL and dependency with version -> Option A

5. Quick Check:

   Use remote repo for custom libs [OK]

Hint: Use remote repo URLs for custom dependencies [OK]

Common Mistakes:

• Using system scope which is deprecated
• Skipping repository URL for custom libs
• Not specifying version for custom dependencies