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
Annotated beans should be discovered in modularized project, if module exports packages to io.micronaut.core.
I know that micronaut could have some issued with JPMS (as mentioned in #6395) but we was able to use it without issues as dependency injection framework for Vertx based application using version 3.x.
Actual Behaviour
Beans are not discovered despite been visible by io.micronaut.core module.
This feature worked correctly in micronaut 3.x.
There were some performance improvements for micronaut 4.0.x in commit #8586 that uses MethodLookup for class loading. Unfortunately MethodLookup.publicLookup() was used that requires package to be accessible from unnamed module.
Steps To Reproduce
No response
Environment Information
No response
Example Application
No response
Version
4.x
The text was updated successfully, but these errors were encountered:
I had modified example micronaut application - https://github.com/karbi/micronaut-example
Please see module-info.java.
Exporting example.micronaut to io.micronaut.context doesn't work as HelloController cannot be found.
If it's exported without restriction - HelloController is discovered.
Expected Behavior
Annotated beans should be discovered in modularized project, if module exports packages to io.micronaut.core.
I know that micronaut could have some issued with JPMS (as mentioned in #6395) but we was able to use it without issues as dependency injection framework for Vertx based application using version 3.x.
Actual Behaviour
Beans are not discovered despite been visible by io.micronaut.core module.
This feature worked correctly in micronaut 3.x.
There were some performance improvements for micronaut 4.0.x in commit #8586 that uses MethodLookup for class loading. Unfortunately MethodLookup.publicLookup() was used that requires package to be accessible from unnamed module.
Steps To Reproduce
No response
Environment Information
No response
Example Application
No response
Version
4.x
The text was updated successfully, but these errors were encountered: