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 ac0029b Regen for commit 27b1f4bfa6819b8ac11c158e73d62474065ba6e8
add 5e8e0ee Regen for commit 27b1f4bfa6819b8ac11c158e73d62474065ba6e8
add c5aad76 Camel-AWS2-Lambda: Producer operations refactoring -
publishVersion
add b053f0e Camel-AWS2-Lambda: Producer operations refactoring -
publishVersion
add cb993d8 Camel-AWS2-Lambda: Producer operations refactoring -
listVersions
add 86ee6e8 Fixed CS
add ffc3fbf Camel-AWS2-Lambda: Producer operations refactoring -
createAlias
add a92cbdf Camel-AWS2-Lambda: Producer operations refactoring -
deleteAlias
add 941954d Camel-AWS2-Lambda: Producer operations refactoring - getAlias
add 26101d0 Camel-AWS2-Lambda: Producer operations refactoring -
listAliases
add a08f45a Fixed CS
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 (ac0029b)
\
N -- N -- N refs/heads/regen_bot (a08f45a)
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/aws2/lambda/Lambda2Producer.java | 276 +++++++++------------
1 file changed, 112 insertions(+), 164 deletions(-)
