This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 0c509abfbcd Regen for commit dbdce79d2cdd3999e8a3af2ecd3985f71c00fba3
add 4349826fa10 Regen for commit bd989118a61a565a636e187f630825fdd54f19b1
add c6e1d553ab1 (chores) camel-test-infra-elasticsearch: retry the
container startup if it fails
add 48449ff2d15 Regen for commit c6e1d553ab1d1603bec39ddac590c3dc70e92c88
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 (0c509abfbcd)
\
N -- N -- N refs/heads/regen_bot (48449ff2d15)
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:
.../endpoint/dsl/AS2EndpointBuilderFactory.java | 228 ++++++++++-----------
.../common/services/ContainerEnvironmentUtil.java | 7 +
.../common/ElasticSearchProperties.java | 4 +
.../ElasticSearchLocalContainerService.java | 4 +
4 files changed, 129 insertions(+), 114 deletions(-)
