jamesnetherton commented on issue #1759:
URL: https://github.com/apache/camel-quarkus/issues/1759#issuecomment-704334368
The problem is that `quarkus-spring-di` has this plugin configuration:
```xml
<plugin>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-bootstrap-maven-plugin</artifactId>
<configuration>
<excludedArtifacts>
<excludedArtifact>org.springframework:spring-core</excludedArtifact>
<excludedArtifact>org.springframework:spring-beans</excludedArtifact>
<excludedArtifact>org.springframework:spring-context</excludedArtifact>
</excludedArtifacts>
</configuration>
</plugin>
```
This effectively bans the core spring libraries from the application. The
Quarkus Spring extensions repackage the Spring dependencies and only include a
minimal set of packages to reduce the overall footprint. Hence we get a CFNE at
runtime.
I don't think there's a simple way to work around this.
We could maybe use a similar approach to Quarkus, where we have our own
custom extensions for `spring-jms` / `spring-jdbc` and repackage the Spring
bits that we depend on. That would get around the artifact ban.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
