-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ArC: add a build item to mark bean archives as known compatible with Quarkus #31856
Conversation
2908a4b
to
b4d7373
Compare
Rebased and marking as ready. |
Failing Jobs - Building b4d7373
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 Windows #📦 integration-tests/gradle✖
✖
⚙️ JVM Tests - JDK 17 Windows #- Failing: extensions/grpc/deployment
! Skipped: extensions/micrometer-registry-prometheus/deployment extensions/micrometer/deployment extensions/opentelemetry/deployment and 44 more 📦 extensions/grpc/deployment✖
|
Failures are known flaky tests, merging. |
@Ladicek maybe I am doing something wrong but I added this to my Processor but still seeing this CDI Lite warning with .Beta1. @BuildStep
void produceKnownCompatible(BuildProducer<KnownCompatibleBeanArchiveBuildItem> knownCompatibleProducer) {
knownCompatibleProducer.produce(new KnownCompatibleBeanArchiveBuildItem("org.omnifaces", "omnifaces"));
} |
@melloware Sorry, was on PTO. Can you point me to a piece of code (maybe a branch of your extension) I can build and try debugging? |
@Ladicek sure I just committed my change to my extension: https://github.com/quarkiverse/quarkus-omnifaces If you run the build you will still see the warnings even though in my processor I have the |
Sorry it took me so long to get to this. I know where the problem is -- I'm using a Fix is simple, see #32213 |
No worries! Thanks for fixing! |
Fixes #31378