This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a change to branch quarkus-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard 38310db47b Add workaround for RemoteCacheManager bean discovery #4841
discard dbcfcc2044 Revert "Revert "Restore smallrye-reactive-messaging-camel
extension""
discard 36426bcd9a Upgrade Quarkus to 3.1.0.CR1
new 5c062219c6 Upgrade Quarkus to 3.1.0.CR1
new a5928adac5 Revert "Revert "Restore smallrye-reactive-messaging-camel
extension""
new 640f2d8ae1 Add workaround for RemoteCacheManager bean discovery #4841
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 (38310db47b)
\
N -- N -- N refs/heads/quarkus-main (640f2d8ae1)
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 3 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:
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
