Chapter 1. Migrating Camel Quarkus projects


1.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.

Important

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.

1.1.1. Prerequisites

  • Roughly 30 minutes
  • JDK installed with JAVA_HOME configured 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.

1.2. Updating with Maven

  1. Configure your extension registry client as described in the Configuring Quarkus extension registry client section of the Quarkus Getting Started guide.
  2. Update with Maven:

    Go to the project directory and update the project to the latest stream:

    1. Ensure that the Quarkus Maven plugin version aligns with the latest supported Red Hat build of Quarkus version.
    2. Run the update with the following command:

      mvn io.quarkus.platform:quarkus-maven-plugin:3.20.0:update -N
      Copy to Clipboard

      For multi-module projects, always first try the following command:

      mvn io.quarkus.platform:quarkus-maven-plugin:3.20.0:update
      Copy to Clipboard

      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.20.0:update -N' \;
      Copy to Clipboard
      Note

      Due 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.2
  3. Analyze the update command output for potential instructions and perform the suggested tasks if needed.
  4. Use a diff tool to inspect all changes.
  5. 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.
  6. Ensure the project builds without errors, all tests pass, and the application functions as required before deploying to production.
  7. Before deploying your updated Quarkus application to production, ensure the following:

    • The project builds without errors.
    • All tests pass.
    • The application functions as required.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat