I've spent quite some time wondering why my integration tests would fail from the command line and not from the IDE. My Application entrypoint would simply be ignored, along with all resources and providers in my main application.
Eventually I'd narrowed this down to a combination of how kumuluz works in exploded mode and the default behaviour of the failsafe plugin, which I use to start and stop a database required for integration tests. The plugin runs after the package phase, hence after the uberjar has been created. Finding a build artefact it adds it to the classpath in lieu of the target/classes. JettyServletServer however expects to look into target\classes in exploded mode, hence fails to pick up the components (unless one adds the current project to scan-libraries, which is totally weird`).
Fortunately, one can configure explicitly this on the failsafeplugin:
I've spent quite some time wondering why my integration tests would fail from the command line and not from the IDE. My
Applicationentrypoint would simply be ignored, along with all resources and providers in my main application.Eventually I'd narrowed this down to a combination of how
kumuluzworks in exploded mode and the default behaviour of thefailsafeplugin, which I use to start and stop a database required for integration tests. The plugin runs after thepackagephase, hence after the uberjar has been created. Finding a build artefact it adds it to the classpath in lieu of thetarget/classes.JettyServletServerhowever expects to look intotarget\classesin exploded mode, hence fails to pick up the components (unless one adds the current project toscan-libraries, which is totally weird`).Fortunately, one can configure explicitly this on the
failsafeplugin:which tells it to prefer
target\classesover the built jar.I'm reporting this because it's obscure and it's worth sharing.