Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.
Get started with understanding multi-threaded applications with our Java Concurrency guide:
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Refactor Java code safely — and automatically — with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
Distributed systems often come with complex challenges such as service-to-service communication, state management, asynchronous messaging, security, and more.
Dapr (Distributed Application Runtime) provides a set of APIs and building blocks to address these challenges, abstracting away infrastructure so we can focus on business logic.
In this tutorial, we'll focus on Dapr's pub/sub API for message brokering. Using its Spring Boot integration, we'll simplify the creation of a loosely coupled, portable, and easily testable pub/sub messaging system:
Get up to speed with the core of Maven quickly, and then go beyond the foundations into the more powerful functionality of the build tool, such as profiles, scopes, multi-module projects and quite a bit more:
1. Overview
Maven is the most commonly used build tool in the Java world. Mainly, it’s just a plugin execution framework in which all jobs are implemented by plugins.
In this tutorial, we’ll give an introduction to the core Maven plugins, providing links to other tutorials focusing on what these plugins can do and how their goals are bound to the build lifecycles.
2. Maven Build Lifecycles
Core plugins closely relate to the build lifecycles.
Maven defines three build lifecycles: default, site and clean. Each lifecycle is composed of multiple phases, which run in order up to the phase specified in the mvn command.
The most important lifecycle is default, responsible for all steps in the build process, from project validation to package deployment.
The site lifecycle is in charge of building a site, showing Maven related information of the project, whereas the clean lifecycle takes care of removing files generated in the previous build.
Many phases in all three lifecycles are automatically bound to the goals of core plugins. The referenced articles will go over these goals and the built-in bindings in detail.
All plugins are enclosed in a build element of the POM:
<build>
<plugins>
<!-- plugins go here -->
</plugins>
</build>3. Plugins Bound to the Default Lifecycle
The built-in bindings of the default lifecycle are dependent on the value of the POM’s packaging element. For the sake of brevity, we’ll go over bindings of the most common packaging types: jar and war.
Here’s a list of the goals that are bound to each phase of the default lifecycle in the format “phase -> plugin:goal”:
- process-resources -> resources:resources
- compile -> compiler:compile
- process-test-resources -> resources:testResources
- test-compile -> compiler:testCompile
- test -> surefire:test
- package -> ejb:ejb or ejb3:ejb3 or jar:jar or par:par or rar:rar or war:war
- install -> install:install
- deploy -> deploy:deploy
The goals above are contained in the following plugins. Follow the links for an article on each of the plugins:
- The Resources Plugin
- The Compiler Plugin
- The Surefire Plugin
- The Failsafe Plugin
- The Verifier Plugin
- The Install Plugin
- The Deploy Plugin
4. Other Plugins
In addition to the plugins mentioned in the previous section, there are two other core plugins whose goals are bound to phases of the site and clean lifecycles:
5. Conclusion
In this article, we went over Maven build lifecycles and provided references to tutorials covering the core plugins of the Maven build tool in detail.
