This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch CAMEL-23667-stub-remote-flag
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 02c6e95e92d0 CAMEL-23667: Update catalog copy of jbang configuration
metadata
discard 2a3eddd89a8d CAMEL-23667: Sync @Metadata stub description with remote
option
discard 3cdee31ebeba CAMEL-23667: Add --stub=remote flag to stub only remote
components via catalog
add 5560aaf1ed8c CAMEL-23674: camel-jbang - Register ExportTypeConverter
for Duration and Short types (#23717)
add 4c7096ecd636 CAMEL-23667: Add --stub=remote flag to stub only remote
components via catalog
add edb1297f7981 CAMEL-23667: Sync @Metadata stub description with remote
option
add 5da061fc70ed CAMEL-23667: Update catalog copy of jbang configuration
metadata
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 (02c6e95e92d0)
\
N -- N -- N refs/heads/CAMEL-23667-stub-remote-flag
(5da061fc70ed)
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:
.../src/main/java/org/apache/camel/main/KameletMain.java | 3 +++
1 file changed, 3 insertions(+)
