Open peteyoungs opened 3 months ago
Hello,
I'm not sure this is valid, as other extensions like kafka-client
don't have separate modules as well: https://github.com/quarkusio/quarkus/blob/main/extensions/kafka-client/deployment/src/main/java/io/quarkus/kafka/client/deployment/DevServicesKafkaProcessor.java
Since the DevService and its transitive dependencies come with the quarkus-logging-splunk-deployment
artifact, it will not be part of the Quarkus runtime classpath (io.testcontainers or org.junit will not appear in target/quarkus-app/lib/main)
The classes will still be loaded during quarkus:build, but DevServicesLoggingSplunkProcessor actual execution can be skipped based on config.
Could you provide more details on why you want to exclude dependencies from the quarkus build classpath ? You'll likely need these dependencies for the QuarkusTests, no ?
Hello,
The dev services PR added a lot of dependencies that we do not want to include in a production application (TestContainers, junit, docker libs etc.) for various reasons including security https://github.com/quarkiverse/quarkus-logging-splunk/pull/242
I am using this extension in keycloak and the application fails to start if those dependencies are excluded due to the presence of
io.quarkiverse.logging.splunk.DevServicesLoggingSplunkProcessor
in the classpath (see error below)All the dev services related code + dependencies should moved into a separate module that can be easily excluded at runtime, as is done for the core quarkus extensions e.g. https://github.com/quarkusio/quarkus/blob/main/extensions/jdbc/jdbc-postgresql/deployment/pom.xml#L26 https://github.com/quarkusio/quarkus/blob/main/extensions/devservices/postgresql/pom.xml