Starting the Maven Build From the Point Where It Failed

Azure Spring Apps is a fully managed service from Microsoft (built in collaboration with VMware), focused on building and deploying Spring Boot applications on Azure Cloud without worrying about Kubernetes.

The Enterprise plan comes with some interesting features, such as commercial Spring runtime support, a 99.95% SLA and some deep discounts (up to 47%) when you are ready for production.

>> Learn more and deploy your first Spring Boot app to Azure.

And, you can participate in a very quick (1 minute) paid user research from the Java on Azure product team.

Slow MySQL query performance is all too common. Of course it is. A good way to go is, naturally, a dedicated profiler that actually understands the ins and outs of MySQL.

The Jet Profiler was built for MySQL only, so it can do things like real-time query performance, focus on most used tables or most frequent queries, quickly identify performance issues and basically help you optimize your queries.

Critically, it has very minimal impact on your server's performance, with most of the profiling work done separately - so it needs no server changes, agents or separate services.

Basically, you install the desktop application, connect to your MySQL server, hit the record button, and you'll have results within minutes:

>> Try out the Profiler

Accelerate Your Jakarta EE Development with Payara Server!

With best-in-class guides and documentation, Payara essentially simplifies deployment to diverse infrastructures.

Beyond that, it provides intelligent insights and actions to optimize Jakarta EE applications.

The goal is to apply an opinionated approach to get to what's essential for mission-critical applications - really solid scalability, availability, security, and long-term support:

>> Download and Explore the Guide (to learn more)

The AI Assistant to boost Boost your productivity writing unit tests - Machinet AI.

AI is all the rage these days, but for very good reason. The highly practical coding companion, you'll get the power of AI-assisted coding and automated unit test generation.
Machinet's Unit Test AI Agent utilizes your own project context to create meaningful unit tests that intelligently aligns with the behavior of the code.
And, the AI Chat crafts code and fixes errors with ease, like a helpful sidekick.

Simplify Your Coding Journey with Machinet AI:

>> Install Machinet AI in your IntelliJ

Looking for the ideal Linux distro for running modern Spring apps in the cloud?

Meet Alpaquita Linux: lightweight, secure, and powerful enough to handle heavy workloads.

This distro is specifically designed for running Java apps. It builds upon Alpine and features significant enhancements to excel in high-density container environments while meeting enterprise-grade security standards.

Specifically, the container image size is ~30% smaller than standard options, and it consumes up to 30% less RAM:

>> Try Alpaquita Containers now.

DbSchema is a super-flexible database designer, which can take you from designing the DB with your team all the way to safely deploying the schema.

The way it does all of that is by using a design model, a database-independent image of the schema, which can be shared in a team using GIT and compared or deployed on to any database.

And, of course, it can be heavily visual, allowing you to interact with the database using diagrams, visually compose queries, explore the data, generate random data, import data or build HTML5 database reports.

>> Take a look at DBSchema

Slow MySQL query performance is all too common. Of course it is. A good way to go is, naturally, a dedicated profiler that actually understands the ins and outs of MySQL.

Critically, it has very minimal impact on your server's performance, with most of the profiling work done separately - so it needs no server changes, agents or separate services.

Basically, you install the desktop application, connect to your MySQL server, hit the record button, and you'll have results within minutes:

>> Try out the Profiler

1. Overview

In this tutorial, we’ll learn how to resume a Maven build after failure. We’ll see how to skip the already successfully built modules. Thus, we’ll jump directly to the point where the issue arose.

2. Example Setup

Let’s build a multi-module Maven project. We call the parent resume-from and the two children lib and business. For the sake of demonstration, we’ll leave the lib project empty. However, the business project contains a lone src/main/java/Main.java file which consists of a Hello World. Let’s now add a dependency to lib in the business module:

<dependency>
    <groupId>com.baeldung</groupId>
    <artifactId>lib</artifactId>
    <version>1.0-SNAPSHOT</version>
</dependency>

As of now, the project’s content is correct, so we can build it successfully:

$ mvn clean install
[...]
[INFO] Reactor Summary for resume-from 1.0-SNAPSHOT:
[INFO]
[INFO] resume-from ........................................ SUCCESS [  1.749 s]
[INFO] lib ................................................ SUCCESS [  2.021 s]
[INFO] business ........................................... SUCCESS [  0.991 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[...]

3. When Running the install Phase

Let’s now remove the semicolon in the Main.java file. This breaks the build of the business submodule:

$ mvn clean install
[...]
[INFO] Reactor Summary for resume-from 1.0-SNAPSHOT:
[INFO]
[INFO] resume-from ........................................ SUCCESS [  1.186 s]
[INFO] lib ................................................ SUCCESS [  0.984 s]
[INFO] business ........................................... FAILURE [  0.334 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.809 s
[INFO] Finished at: 2023-06-20T16:15:13+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project business: Compilation failure
[ERROR] [...]/resume-from/business/src/main/java/Main.java:[4,43] ';' expected
[...]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :business

As the lib submodule was built successfully, it would be nice to skip its build after we fix the problem. As said in Maven’s error message, we can use the -rf option to resume the reactor from a given module. Let’s fix the Main.java file and try this:

$ mvn clean install -rf :business
[INFO] Scanning for projects...
[INFO]
[INFO] -----------------------< com.baeldung:business >------------------------
[INFO] Building business 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[...]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  1.318 s
[INFO] Finished at: 2023-06-20T17:21:07+02:00
[INFO] ------------------------------------------------------------------------

As expected, only the business submodule was built this time. Actually, -rf is the short version of –resume-from, so we could write equivalently:

$ mvn clean install --resume-from :business

4. When Not Running install

Let’s now suppose that instead of running a Maven install, we stop the build at an earlier phase. To showcase this, we can come back to the situation where the Main.java file is corrupted. Let’s also clean up our local repository and run the package phase:

$ mvn clean package
[...]
[INFO] Reactor Summary for resume-from 1.0-SNAPSHOT:
[INFO]
[INFO] resume-from ........................................ SUCCESS [  0.108 s]
[INFO] lib ................................................ SUCCESS [  0.709 s]
[INFO] business ........................................... FAILURE [  0.316 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.216 s
[INFO] Finished at: 2023-06-20T17:49:59+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project business: Compilation failure
[ERROR] [...]/resume-from/business/src/main/java/Main.java:[4,43] ';' expected
[...]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :business

Unsurprisingly, we get the same compilation error. The error message gives us the same hint to use the -rf option after fixing the problem. Thus, let’s fix the problem and run this command:

$ mvn clean package -rf :business
[INFO] Scanning for projects...
[INFO]
[INFO] -----------------------< com.baeldung:business >------------------------
[INFO] Building business 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for com.baeldung:lib:jar:1.0-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.187 s
[INFO] Finished at: 2023-06-20T17:56:34+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project business: Could not resolve dependencies for project com.baeldung:business:jar:1.0-SNAPSHOT: Could not find artifact com.baeldung:lib:jar:1.0-SNAPSHOT -> [Help 1]

Since we didn’t run the install phase, the lib submodule wasn’t installed in our local repository during the first build. Thus, Maven can’t find the lib artifact when trying to resume the build. Theoretically, we could solve this problem by adding the –also-make option to our command line. With –also-make, Maven is supposed to build all projects that business depends on. However, there is a bug in Maven 3, and –also-make is ignored when used in conjunction with –resume-from.

This bug will be fixed in Maven 4, which is currently still in development. Meanwhile, we can’t resume the reactor from a particular module in this case. Unfortunately, we need to redo the entire build:

$ mvn clean package
[...]
[INFO] Reactor Summary for resume-from 1.0-SNAPSHOT:
[INFO]
[INFO] resume-from ........................................ SUCCESS [  0.109 s]
[INFO] lib ................................................ SUCCESS [  0.660 s]
[INFO] business ........................................... SUCCESS [  0.436 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[...]

5. Conclusion

In this article, we saw how to skip parts of a Maven build after it failed. When we install the submodules into the local repository, we can use the -rf option. On the other hand, not installing them leads to needing to redo the whole build because of a Maven bug.

As always, the code is available over on GitHub.

Starting the Maven Build From the Point Where It Failed

Get started with Spring and Spring Boot, through the Learn Spring course:

1. Overview

2. Example Setup

3. When Running the install Phase

4. When Not Running install

5. Conclusion

Get started with Spring and Spring Boot, through the Learn Spring course:

REST with Spring

Learn Spring Security ▼▲

Learn Spring Security Core

Learn Spring Security OAuth

Learn Spring

Learn Spring Data JPA

Persistence

REST

Security

Full Archive

Baeldung Ebooks

About Baeldung

Write for Baeldung

Get started with Spring and Spring Boot, through the Learn Spring course:

1. Overview

2. Example Setup

3. When Running the install Phase

4. When Not Running install

5. Conclusion

Get started with Spring and Spring Boot, through the Learn Spring course: