This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch quarkus-master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard d173775 Upgrade to Quarkus 1.8.0 - WIP
add 3e7862d Completed bean itests with an @InjectMock test
add 8644281 Fixed typos
add 6f7f29b Avoid purging artifacts for builds that may be in progress
new d5764b5 Upgrade to Quarkus 1.8.0 - WIP
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 (d173775)
\
N -- N -- N refs/heads/quarkus-master (d5764b5)
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 1 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:
.github/workflows/purge-stale-artifacts-cron.yaml | 3 +-
docs/modules/ROOT/pages/user-guide/bootstrap.adoc | 2 +-
docs/modules/ROOT/pages/user-guide/cdi.adoc | 2 +-
.../spi/CamelBootstrapCompletedBuildItem.java | 2 +-
.../quarkus/main/events/BeforeInitialize.java | 2 +-
integration-tests/bean/pom.xml | 5 +++
.../component/bean/BeanInjectMockTest.java} | 43 ++++++++++++----------
7 files changed, 35 insertions(+), 24 deletions(-)
copy
integration-tests/{openapi-java/src/test/java/org/apache/camel/quarkus/component/openapijava/it/OpenApiTest.java
=>
bean/src/test/java/org/apache/camel/quarkus/component/bean/BeanInjectMockTest.java}
(53%)
