You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing camel-quarkus with Quarkus 2.0.0.Alpha2, I noticed a number of test failures that seem to be related to the loading of classpath resources.
The problems occur where we do some pre-test setup work within a QuarkusTestResourceLifecycleManager impl. If some third party lib attempts to load a resource from the classpath, it appears to be failing.
For example, we use org.apache.ftpserver to set up a local FTP server and pass it a keystore to configure security. The loading of the keystore from the classpath fails. E.g the FTP library does:
Describe the bug
Testing camel-quarkus with Quarkus 2.0.0.Alpha2, I noticed a number of test failures that seem to be related to the loading of classpath resources.
The problems occur where we do some pre-test setup work within a
QuarkusTestResourceLifecycleManager
impl. If some third party lib attempts to load a resource from the classpath, it appears to be failing.For example, we use
org.apache.ftpserver
to set up a local FTP server and pass it a keystore to configure security. The loading of the keystore from the classpath fails. E.g the FTP library does:Similarly, some tests that use testcontainers also fail where testcontainers tries to load a resource from the classpath.
This was previously working fine in 2.0.0.Alpha1.
Expected behavior
Classpath resource loading works successfully.
Actual behavior
null
is returned fromgetResource
/getResourceAsStream
etc. E.g in the case of the aforementioned FTP server exampleTo Reproduce
mvn clean test
. Note the console message:2.0.0.Alpha1
and observe success.mvn clean test -Dquarkus.platform.version=2.0.0.Alpha1
.The text was updated successfully, but these errors were encountered: