ApplicationModuleTest seems to block EntityScan packages

[ivanfryda]

Hello,

My application has a @EntityScan with my root package and a Spring Modulith package and a couple of Axon packages. My ApplicationModuleTest fails since it does not have the Axon entities in the JPA Metamodel. How can I tell ApplicationModuleTest not to restrict it? Or maybe this is beyond the scope of it and I should test this differently?

[odrotbohm]

This is a shortcoming of @EntityScan, already reported with Spring Boot here.

[ivanfryda]

But the issue still persists if I replace EntityScan with AutoConfigurationPackage. Are there any recommended/possible workarounds?

[odrotbohm]

Can you elaborate why you'd need to explicitly list the Axon packages as entity packages? Is that generated code? If so, why is it not generated into the module's packages or – if shared – into the package of a core module that's declared as shared module?

[ivanfryda]

I just figured I don't need to do that in order for Axon to work, in fact I'd argue that using EntityScan should be avoided whenever possible. I was able to get it all configured "automatically" with minimal intervention.

[odrotbohm]

That's great to hear. Happy coding! 🚀