This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch camel-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard 0015706 Temporary hacks to handle version misalignment of
smallrye-health and smallrye-faulttolerance in Quarkus & Camel
discard 6d6fe7a Upgrade Camel to 3.16.0
add e5a4988 Remove freemarker inaccurate documentation
add 78aaf9d Fixup e72113e send optaplanner test messages asynchronously
add 0c07d1a Fix link to Quarkus Freemarker docs
add 0b7c1fd Updated CHANGELOG.md
new df29585 Upgrade Camel to 3.16.0
new 21b9941 Temporary hacks to handle version misalignment of
smallrye-health and smallrye-faulttolerance in Quarkus & Camel
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 (0015706)
\
N -- N -- N refs/heads/camel-main (21b9941)
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 2 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 ++
.../pages/reference/extensions/freemarker.adoc | 44 +---------------------
.../runtime/src/main/doc/configuration.adoc | 44 +---------------------
.../optaplanner/it/OptaplannerResource.java | 6 ++-
4 files changed, 9 insertions(+), 88 deletions(-)
