This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch task-36-1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 1e9197db858d Regen
discard 6e3c608847e7 CAMEL-23107 - camel-docling - Add CLI command validation
in buildDoclingCommand
add efb623071b73 CAMEL-23107 - camel-docling - Add CLI command validation
in buildDoclingCommand
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 (1e9197db858d)
\
N -- N -- N refs/heads/task-36-1 (efb623071b73)
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:
.../camel/component/docling/DoclingProducer.java | 13 +++++-------
...t.java => DoclingCustomArgsValidationTest.java} | 24 ++++++++--------------
2 files changed, 14 insertions(+), 23 deletions(-)
rename
components/camel-ai/camel-docling/src/test/java/org/apache/camel/component/docling/{DoclingCliInjectionTest.java
=> DoclingCustomArgsValidationTest.java} (86%)
