This is an automated email from the ASF dual-hosted git repository.
ppalaga pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard 58aab30 Increase Jira extension test coverage
discard 491e88b Fix WatchUpdatesConsumer in native mode
discard d2c29c7 Add camel-quarkus-support-spring to jira extension
discard f6bbc7d Exclude jersey from jira extension and use the
quarkus-rest-client
omit 941b489 Next is 2.0.0
new 08b1348 Next is 2.0.0
new 5d69f1d Exclude jersey from jira extension and use the
quarkus-rest-client
new 57f0872 Add camel-quarkus-support-spring to jira extension
new 4abf229 Fix WatchUpdatesConsumer in native mode
new 307e671 Increase Jira extension test coverage
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 (58aab30)
\
N -- N -- N refs/heads/main (307e671)
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.
The 5 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../src/generated/resources/org/apache/camel/component/qute/qute.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
