-
Bug
-
Resolution: Done
-
Critical
-
2.13.3.ER3
-
False
-
None
-
False
-
+
-
-
---
-
-
When running our `startstop-ts-acceptance-code-quarkus`job, test `CodeQuarkusTest#supportedExtensionsSubsetA` that uses combination of 18 extensions:
- QUARKUS_RESTEASY_REACTIVE
- QUARKUS_RESTEASY_REACTIVE_JSONB
- QUARKUS_RESTEASY_REACTIVE_JACKSON
- QUARKUS_RESTEASY_REACTIVE_QUTE
- QUARKUS_REST_CLIENT_REACTIVE
- QUARKUS_REST_CLIENT_REACTIVE_JACKSON
- QUARKUS_REST_CLIENT_REACTIVE_JAXB
- QUARKUS_REST_CLIENT_REACTIVE_JSONB
- QUARKUS_OIDC_CLIENT_REACTIVE_FILTER
- QUARKUS_HIBERNATE_VALIDATOR
- QUARKUS_HIBERNATE_ORM_REST_DATA_PANACHE
- QUARKUS_REACTIVE_ROUTES
- QUARKUS_SMALLRYE_GRAPHQL
- QUARKUS_SMALLRYE_GRAPHQL_CLIENT
- QUARKUS_SMALLRYE_JWT
- QUARKUS_SMALLRYE_OPENAPI
- QUARKUS_UNDERTOW
- QUARKUS_WEBSOCKETS
build fails over missing artifact `com.google.guava:listenablefuture:jar:9999.0.0.empty-to-avoid-conflict-with-guava-redhat-00001`. Apart of the fact that artifact is missing, naming is super suspicious.
Update: naming comes from upstream - https://repo1.maven.org/maven2/com/google/guava/guava/31.1-jre/guava-31.1-jre.pom