Replies: 2 comments
-
Have tried bootstrapping all modules, and that doesn't help. |
Beta Was this translation helpful? Give feedback.
0 replies
-
#82 - holds the keys for resolution, add @modulith, and shared modules. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just testing out Spring Modulith, and is very promising so far.
The issue that I am facing is a little strange, Spring Module verification throws 'NoSuchBeanDefinitionException' for beans contained in 'certain packages'; I think the packages that don't have a direct relation to other exposed modules.
I have this repo where when I run the verification of application modules 'test', it fails as it is unable to instantiate the AuditingEntityConfig (NoSuchBeanDefinitionException)
Here is the AuditingEntityConfig
Interestingly, if I make both the AuditorAware and the DateTimeProvider beans as 'static', the module verification passes, I don't intend to override application container by making beans static, just done for testing.
It appears to be case of how SpringModuleTests isolate and test modules to ensure no cross-dependencies; how do let the application module tests that I have a common package that has beans, which are ok to be instantiated as part of all modules tests?
Beta Was this translation helpful? Give feedback.
All reactions