Red Hat SummitChapter 4. Migrating Camel Quarkus projects
4.1. Updating projects to the latest Quarkus version
We recommend that you use Maven to update and upgrade your projects to the latest Quarkus version.
For projects that use Hibernate ORM or Hibernate Reactive, review the Hibernate ORM 5 to 6 migration quick reference. The following update command covers only a subset of this guide.
4.1.1. Prerequisites
- Roughly 30 minutes
-
JDK installed with
JAVA_HOMEconfigured appropriately - Apache Maven 3.8.6
- Optionally, the Quarkus CLI if you want to use it
- A project based on Camel Quarkus version 2.13 or later.
4.1.2. Updating with Maven
- Configure your extension registry client as described in the Configuring Quarkus extension registry client section of the Quarkus Getting Started guide.
Update with Maven:
Go to the project directory and update the project to the latest stream:
- Ensure that the Quarkus Maven plugin version aligns with the latest supported Red Hat build of Quarkus version.
Run the update with the following command:
mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update -N
For multi-module projects, always first try the following command:
mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update
If this command fails, you can instead try this longer command:
find . -type f -name "pom.xml" -execdir sh -c 'mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update -N' \;
NoteDue to an issue with OpenRewrite, warnings are preset in the migration log.
- Optional
By default, this command updates to the latest current version. To update to a specific stream instead of latest current version, add the stream option to this command followed by the version; for example:
-Dstream=3.2NoteUpdates of multi-module project may show a lot of errors, because the update tool fails to update modules with
<packaging>pom</packaging>.If such modules are present (typically containing versions), update them manually.
- Analyze the update command output for potential instructions and perform the suggested tasks if needed.
- Use a diff tool to inspect all changes.
- Review the migration guide for items that were not updated by the update command. If your project has such items, implement the additional steps advised in these topics.
- Ensure the project builds without errors, all tests pass, and the application functions as required before deploying to production.
Before deploying your updated Quarkus application to production, ensure the following:
- The project builds without errors.
- All tests pass.
- The application functions as required.
