discard 3402497 Upgrade to Quarkus 1.12.0.Final
add 0662dd6 Add vertx-kafka component support
add 3bc47e2 Use consistent Kafka docker image version
add ceb614d Improve exception handling in ExtendDefaultTrustStore
add ae3dce1 add missing QuarkusTestResource
add 149fcd2 Ensure JDK is set up for reporting step in nightly branch sync workflows
add 305c1b1 Add notes on enabling Geolocation APIs for geocoder extension integration tests
add d17bf28 Minio native support #2040
new d939ea8 Upgrade to Quarkus 1.12.0.Final
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 (3402497)
N -- N -- N refs/heads/quarkus-master (d939ea8)
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.