Have you ever tried running Maven phases in different stages/jobs of a CI pipeline? If so, you have probably run into an annoying issue where Maven re-runs the phases already executed in previous jobs, even though the files produced by the previous phase are present. Let’s see how to fix that!
After quite a few releases fixing security vulnerabilities on the 26.7.x branch, here comes 26.8.0. Lots of new features this time. Let’s go through the ones I find the most interesting.
Even though it brings more trouble than anything else, we are going to see how to enable Secure Boot on a Linux distribution such as Pop!_OS with the rEFInd boot manager. The principle should be the same with GRUB, namely signing the entire boot chain.
In the previous article, we discussed how to automatically launch a container that exposes an API connected to its own database using a Quarkus extension. Now, we will explore how to communicate with this API from our main application.
In the previous article, we saw how to automatically launch a database using a Quarkus extension. Now, we will see how to start our service in the same way and make it use the database we just deployed. I won’t go over the points covered in the previous article, so I encourage you to read it before continuing.
Today, we’re tackling a major topic with a use case that is not documented by Quarkus but is extremely useful. Quarkus offers extensions with “dev services.” Once included in your project, these extensions automatically launch services when the project starts in dev mode. We will see how to create our own “dev service” for Quarkus applications. The idea is to provide an extension for each of our services to make them easily usable by others.
LE BARO Romain