This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a change to branch fix-jbang-metadata-mojo
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 1aa5cf6d28c0 Revert gulpfile changes (moved to PR #22292)
discard 31d3ec755538 Fix resilientSrc to continue after ENOENT instead of
aborting stream
discard e8e056eb1ffb Add diagnostic logging to gulp symlink tasks
discard eda6847ff3ad Avoid deep glob traversal in DSL docs pattern
discard 9848fc643da7 Remove src.unpipe() call that fails on vinyl streams
discard 3cd43c431d49 Fix gulp task hanging on ENOENT by using passthrough
stream
discard 5ea9ec8a5c16 Fix ENOENT handling in docs gulp build
discard e215f0a501a4 Add missing JavaSource import to avoid FQCN usage
discard 74dc68c12f83 Resolve picocli completion candidates in generated docs
discard c0f74cd6c70a Ignore .camel-jbang directories in docs gulp build
discard 1cff3d01310b Regenerate jbang command docs and metadata after merge
with main
add 506b03a96302 Resolve picocli completion candidates and add missing
import
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 (1aa5cf6d28c0)
\
N -- N -- N refs/heads/fix-jbang-metadata-mojo (506b03a96302)
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:
