This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a change to branch camel-master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
omit d84684d Exclude service ThreadPoolProfileConfigurationProperties as
it references a non-existent class
omit 662b709 health example - requires Camel 3.4 (#1321)
omit 5caaa72 microprofile-health extensions should create health registry
and initialize it at built time. Requires Camel 3.4.0
omit b28e928 Upgrade to Camel 3.4.0
add 74089b5 Upgrade to Camel 3.4.0
add 23b2f9c microprofile-health extensions should create health registry
and initialize it at built time. Requires Camel 3.4.0
add 0241617 health example - requires Camel 3.4 (#1321)
add 9d990df Exclude service ThreadPoolProfileConfigurationProperties as
it references a non-existent class
new 1ee7988 Upgrade to Camel 3.5.0-SNAPSHOT
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 (d84684d)
\
N -- N -- N refs/heads/camel-master (1ee7988)
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 1 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:
pom.xml | 2 +-
poms/bom/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
