Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Migrating Camel Quarkus projects

Red Hat build of Apache Camel 4.8

Migrating Camel Quarkus projects

Abstract

Migrating Camel Quarkus projects provides information on migrating from Red Hat Fuse 7 to Red Hat build of Apache Camel for Quarkus.

Preface
링크 복사

Providing feedback on Red Hat build of Apache Camel documentation

To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account.

Procedure

  1. Click the following link to create ticket
  2. Enter a brief description of the issue in the Summary.
  3. Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
  4. Clicking Submit creates and routes the issue to the appropriate documentation team.

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.15.4.redhat-00001:update -N
      Copy to Clipboard Toggle word wrap

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

      mvn io.quarkus.platform:quarkus-maven-plugin:3.15.4.redhat-00001:update
      Copy to Clipboard Toggle word wrap

      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.15.4.redhat-00001:update -N' \;
      Copy to Clipboard Toggle word wrap
      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.

    Note

    In some cases versions might not upgrade correctly, and may not match the migration to Quarkus.

    If so, you must change the version manually. See Migrating Apache Camel for instructions.

  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.

Legal Notice
링크 복사

Copyright © 2025 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat맨 위로 이동