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 350f106 Regen for commit 30c760e15ad0aef26021408e484ede6851e21de8
add e2bda73 CAMEL-16353: camel-main - Add @EagerClassloaded to mark
classes which should be eager loaded via camel-main. This optimize to load
these classes before Camel is started and otherwise would load these classes on
first message processed. A maven plugin scans the code and updates the source
code to keep the list of classes to eager loaded automatic up-to-date.
add 4f3fb76 Regen for commit e2bda73c4f80b98fea4a19b7ca5fcc04224ff70e
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 (350f106)
\
N -- N -- N refs/heads/regen_bot (4f3fb76)
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:
.../java/org/apache/camel/spi/annotations/EagerClassloaded.java | 9 +++++++++
.../java/org/apache/camel/spi/annotations/EagerClassloaded.java | 9 +++++++++
2 files changed, 18 insertions(+)
