This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch chore/camel-launcher-its-not-quickly
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 7f39d00a97ad chore: camel-launcher - run the distribution ITs in
verify, not with -Dquickly, and in the native exe workflow
add e45558b86144 CAMEL-26488: camel-mina - close the synchronous producer
session when a request times out (#28865)
add 9c2f59172db1 chore(deps): Bump
io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17 from
2.33.0-alpha to 2.33.1-alpha (#28875)
add 024c8ec9251f chore: package-native validation - build
camel-yaml-dsl-validator from source (#28886)
add 35699e762092 chore: camel-launcher - run the distribution ITs in
verify, not with -Dquickly, and in the native exe workflow
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 (7f39d00a97ad)
\
N -- N -- N refs/heads/chore/camel-launcher-its-not-quickly
(35699e762092)
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:
.github/workflows/package-native-validation.yml | 8 ++++++--
.../java/org/apache/camel/component/mina/MinaProducer.java | 10 ++++++----
.../camel/component/mina/MinaDisconnectOnTimeOutTest.java | 7 ++++---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc | 10 ++++++++++
parent/pom.xml | 2 +-
5 files changed, 27 insertions(+), 10 deletions(-)
