This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a change to branch quarkus-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard e400ef228d Temporarily work around Vert.x incompatibilities between
Camel & Quarkus
discard 779a628de8 Disable OptaPlanner native profile due to #3899
discard aa0ef7e36f Upgrade Quarkus to 2.11.0.CR1
add 5ed9420534 dozer: Deprecate the typeConverterEnabled config #3900
add 4a2c68e699 Updated CHANGELOG.md
new 378c4ea1a4 Upgrade Quarkus to 2.11.0.CR1
new 01e24373ef Disable OptaPlanner native profile due to #3899
new 44b1b3e8eb Temporarily work around Vert.x incompatibilities between
Camel & Quarkus
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (e400ef228d)
\
N -- N -- N refs/heads/quarkus-main (44b1b3e8eb)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
CHANGELOG.md | 3 +++
docs/modules/ROOT/pages/reference/extensions/dozer.adoc | 6 ------
.../org/apache/camel/quarkus/component/dozer/CamelDozerConfig.java | 1 +
.../apache/camel/quarkus/component/fop/deployment/FopProcessor.java | 2 ++
4 files changed, 6 insertions(+), 6 deletions(-)
