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 6f536f3281 Fixed aws2-kinesis
discard b6aedcbdbe generated poms
discard 08c8091902 Fixed web3j + generated poms
discard af0693a188 Fixed arangodb + generated pomns
discard 72ddabb791 enabled ssh
discard ad41af24b4 Fixed - the following artifacts could not be resolved:
io.atlassian.fugue:fugue-parent:pom:5.0.0
discard a628accd99 Fixed Atom
discard 27d134ae61 Fixed ArangoDB and google-secret-manager version conflict +
generated poms
discard 3ba4a9e91c Proper fix of tika version conflict + generated poms
discard 1078609654 Fixed tika version conflict + regen of poms
discard 4df5185433 POM regen
discard 4c96358e0c Workaround for dataformat (because of iCal4j update - #5099
discard 235a28ea0b generated poms
discard a3df65ca73 Fixed Slack
discard 5ccc91c9c3 Fixed twitter + generated stuff.
discard 7f063c76d2 generated POMs
discard 25e3849301 fixed debezium version problem
discard 4622a74b05 Fixed version conflict + substitution in json-validator
discard c124bece99 fixed optaplanner version conflict + generated files
discard e637a414c9 synced + generated files
discard da1624ebb6 Upgrade Camel to 4.0.0
add 9ac6ee8f91 Do not produce JmxMeterRegistry bean in native mode testing
add fb1eaa11db Upgrade Quarkus to 3.2.2.Final
new eb5b0817f7 Upgrade Camel to 4.0.0
new d0ae9b988d synced + generated files
new 5a9f64f870 fixed optaplanner version conflict + generated files
new 1ac2b11fb5 Fixed version conflict + substitution in json-validator
new 635574c8c7 fixed debezium version problem
new 69002a0390 generated POMs
new f626565b1b Fixed twitter + generated stuff.
new 3bdda5a03f Fixed Slack
new f3b3b49e85 generated poms
new cc41eb9ef1 Workaround for dataformat (because of iCal4j update - #5099
new 9021f18628 POM regen
new ae750ddc1e Fixed tika version conflict + regen of poms
new 047db3413c Proper fix of tika version conflict + generated poms
new a345b12ae7 Fixed ArangoDB and google-secret-manager version conflict +
generated poms
new 6812f79a1c Fixed Atom
new d583ec9d7f Fixed - the following artifacts could not be resolved:
io.atlassian.fugue:fugue-parent:pom:5.0.0
new bf42e3879a enabled ssh
new bbe457e96a Fixed arangodb + generated pomns
new 563ba7df59 Fixed web3j + generated poms
new 021b7b8c67 generated poms
new 8630e84ada Fixed aws2-kinesis
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 (6f536f3281)
\
N -- N -- N refs/heads/camel-main (8630e84ada)
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 21 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:
docs/antora.yml | 2 +-
.../camel/quarkus/component/micrometer/it/MicrometerProducers.java | 2 ++
pom.xml | 2 +-
3 files changed, 4 insertions(+), 2 deletions(-)
