Make check for RESTEasy Classic stricter

Fixes: quarkusio#33360
manofthepeace · May 16, 2023 · 3aa6382 · 3aa6382
1 parent 2bc7f4e
commit 3aa6382
Showing 1 changed file with 4 additions and 1 deletion.
diff --git a/.../java/io/quarkus/resteasy/reactive/common/deployment/ResteasyReactiveCommonProcessor.java b/.../java/io/quarkus/resteasy/reactive/common/deployment/ResteasyReactiveCommonProcessor.java
@@ -46,6 +46,7 @@
 import io.quarkus.arc.deployment.BeanContainerBuildItem;
 import io.quarkus.arc.deployment.BuildTimeConditionBuildItem;
 import io.quarkus.arc.deployment.GeneratedBeanBuildItem;
+import io.quarkus.bootstrap.classloading.QuarkusClassLoader;
 import io.quarkus.deployment.Capabilities;
 import io.quarkus.deployment.Capability;
 import io.quarkus.deployment.annotations.BuildProducer;
@@ -79,7 +80,9 @@ public class ResteasyReactiveCommonProcessor {
     @BuildStep
     void searchForProviders(Capabilities capabilities,
             BuildProducer<AdditionalApplicationArchiveMarkerBuildItem> producer) {
-        if (capabilities.isPresent(Capability.RESTEASY) || capabilities.isPresent(Capability.REST_CLIENT)) {
+        if (capabilities.isPresent(Capability.RESTEASY) || capabilities.isPresent(Capability.REST_CLIENT)
+                || QuarkusClassLoader.isClassPresentAtRuntime(
+                        "org.jboss.resteasy.reactive.server.injection.JaxrsServerFormUrlEncodedProvider")) { // RESTEasy Classic could be imported via non-Quarkus dependencies
             // in this weird case we don't want the providers to be registered automatically as this would lead to multiple bean definitions
             return;
         }