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


 discard a59f3002bff Regen for commit 2746a38d98a4de04c80f264b31b8d4e55bef1ab9
     add 890a3e1537f CAMEL-17861 (#7493)
     add e0fcb229e87 CAMEL-18063: camel-jbang - Using --deps for debug may 
store null as GAV version
     add 051ea29efba Regen for commit 00094fca48cf5265ae75fc19ce1c4b160ae93ea2
     add a482b291384 Regen for commit 051ea29efba69afe4fd9a3631302a2b97c846b68

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   (a59f3002bff)
            \
             N -- N -- N   refs/heads/regen_bot (a482b291384)

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:
 .../org/apache/camel/component/aws2/s3/utils/AWS2S3Utils.java    | 8 ++++++++
 .../org/apache/camel/component/azure/storage/blob/BlobUtils.java | 2 +-
 .../src/main/java/org/apache/camel/main/MavenGav.java            | 9 +++++++++
 3 files changed, 18 insertions(+), 1 deletion(-)

Reply via email to