This is an automated email from the ASF dual-hosted git repository.
ppalaga pushed a change to branch camel-4
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
omit e3d2eb09b0 Workaround #4490 REST-Assured does not support JSON-B
3.0/Jakarta EE 10
omit 2524ee8c53 Require Java 17
omit bb51eb883d Avoid creating quarkus.log files in module directories
omit c651e0916f Upgrade to Camel 4.0.0 and Quarkus 3.0.0.Alpha3
add a0a0027fa4 Upgrade to Camel 4.0.0 and Quarkus 3.0.0.Alpha3
add 081523ae0c Avoid creating quarkus.log files in module directories
add 11b199dca9 Require Java 17
add c62bddb414 Workaround #4490 REST-Assured does not support JSON-B
3.0/Jakarta EE 10
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 (e3d2eb09b0)
\
N -- N -- N refs/heads/camel-4 (c62bddb414)
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.
No new revisions were added by this update.
Summary of changes:
.../component/dataformats/jackson/json/JacksonJsonRoute.java | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
