POM.xml and dependencies in Spring Boot - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the packaging type in a POM.xml file.

Spring Boot

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.example</groupId>
  <artifactId>demo</artifactId>
  <version>1.0.0</version>
  <packaging>[1]</packaging>
</project>

Drag options to blanks, or click blank then click option'

Ajar

Bexe

Czip

Dbin

Attempts:

3 left

💡 Hint

Common Mistakes

Using unsupported packaging types like exe or zip.

Leaving the packaging tag empty.

The <packaging> tag defines the output type of the build. For Spring Boot projects, jar is the standard packaging.

2fill in blank

medium

Complete the code to add the Spring Boot starter web dependency in POM.xml.

Spring Boot

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>[1]</artifactId>
  <version>3.0.0</version>
</dependency>

Drag options to blanks, or click blank then click option'

Aspring-boot-starter-web

Bspring-boot-starter-data-jpa

Cspring-boot-starter-security

Dspring-boot-starter-test

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a starter for database or security instead of web.

Forgetting to specify the artifactId.

The spring-boot-starter-web dependency includes everything needed to build web applications with Spring Boot.

3fill in blank

hard

Fix the error in the dependency declaration by completing the missing tag.

Spring Boot

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

Drag options to blanks, or click blank then click option'

A<type>jar</type>

B<scope>compile</scope>

C<optional>true</optional>

D<version>3.0.0</version>

Attempts:

3 left

💡 Hint

Common Mistakes

Using <scope> instead of <version> when version is missing.

Omitting the version tag entirely.

The <version> tag specifies which version of the dependency to use. Without it, Maven may not know which version to download.

4fill in blank

hard

Fill both blanks to add a dependency with groupId and artifactId correctly.

Spring Boot

<dependency>
  <groupId>[1]</groupId>
  <artifactId>[2]</artifactId>
</dependency>

Drag options to blanks, or click blank then click option'

Aorg.springframework.boot

Borg.apache.commons

Cspring-boot-starter-security

Dcommons-lang3

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing groupId and artifactId values.

Using unrelated groupId with a Spring Boot artifactId.

The groupId org.springframework.boot and artifactId spring-boot-starter-security together specify the Spring Boot security starter dependency.

5fill in blank

hard

Fill all three blanks to create a dependency with groupId, artifactId, and version.

Spring Boot

<dependency>
  <groupId>[1]</groupId>
  <artifactId>[2]</artifactId>
  <version>[3]</version>
</dependency>

Drag options to blanks, or click blank then click option'

Aorg.projectlombok

Blombok

C1.18.26

D2.0.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect version numbers.

Swapping artifactId and groupId.

This dependency adds Lombok, a popular Java library that helps reduce boilerplate code. The version 1.18.26 is a stable recent release.

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