This is an automated email from the ASF dual-hosted git repository.
ppalaga pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/main by this push:
new 6202618 Migration guide: mention Quarkus 2.0 migration guide,
camel-quarkus-xml-io artifact replaced by camel-quarkus-xml-io-dsl
6202618 is described below
commit 620261806a6b5f42204908fb975bdea2339e9775
Author: Peter Palaga <[email protected]>
AuthorDate: Tue Jun 22 18:27:28 2021 +0200
Migration guide: mention Quarkus 2.0 migration guide,
camel-quarkus-xml-io artifact replaced by camel-quarkus-xml-io-dsl
---
docs/modules/ROOT/pages/migration-guide/2.0.0.adoc | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/migration-guide/2.0.0.adoc
b/docs/modules/ROOT/pages/migration-guide/2.0.0.adoc
index a2819b6..0eb5734 100644
--- a/docs/modules/ROOT/pages/migration-guide/2.0.0.adoc
+++ b/docs/modules/ROOT/pages/migration-guide/2.0.0.adoc
@@ -2,6 +2,10 @@
The following guide outlines how to adapt your code to changes that were made
in Camel Quarkus 2.0.0 & Quarkus 2.0.0.Final.
+== Changes in Quarkus
+
+Please refer to
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.0[Quarkus 2.0.0
Migration Guide].
+
== Changes to the observability HTTP endpoint paths
In Quarkus 1.x, health and metrics endpoints were available at `/metrics` &
`/health` context paths. In Quarkus 2.x this has changed with the addition of a
mandatory `/q` path prefix. The endpoints are
@@ -10,7 +14,7 @@ now accessible at the following URLs.
* http://localhost:8080/q/health
* http://localhost:8080/q/metrics
-== `camel-quarkus-main` removed
+== `camel-quarkus-main` artifact removed
Before Camel Quarkus 1.8.0, `camel-quarkus-main` used to be a full blown
separate artifact.
In 1.8.0, all functionality of `camel-quarkus-main` was moved to
`camel-quarkus-core`,
@@ -20,6 +24,12 @@ The empty `camel-quarkus-main` artifact was removed
completely in Camel Quarkus
As long as your application depends on any other Camel Quarkus extension, it
is enough to remove the `camel-quarkus-main` dependency.
This is because all Camel Quarkus extensions transitively depend on
`camel-quarkus-core` where the the original `camel-quarkus-main` functionality
is hosted now.
+== `camel-quarkus-xml-io` artifact replaced by `camel-quarkus-xml-io-dsl`
+
+The functionality available in `camel-quarkus-xml-io` was moved to
`camel-quarkus-xml-io-dsl` in Camel Quarkus 1.8.0.
+Since that version `camel-quarkus-xml-io` was deprecated and was kept only for
backwards compatibility reasons as an empty wrapper around
`camel-quarkus-xml-io-dsl`.
+`camel-quarkus-xml-io` was removed fully in Camel Quarkus 2.0.0 and you'll
have to use `camel-quarkus-xml-io-dsl` as a replacement.
+
== `quarkus.camel.native.resources.*` replaced by
`quarkus.native.resources.includes`
The `quarkus.camel.native.resources.include-patterns` and
`quarkus.camel.native.resources.exclude-patterns` configuration properties were
removed in Camel Quarkus 2.0.0.
