Sébastien Deleuze

Results 578 comments of Sébastien Deleuze

You can use `NativeHint(options = "--trace-object-instantiation=org.apache.commons.logging.impl.SLF4JLocationAwareLog")`. Feel free to comment if you think we should update default initialization hint based on your findings.

We are progressing on that one, with a collaboration with GraalVM team on Netty, but that will take more time than expected so I bring back this one to the...

@nyakaz73 Something is likely wrong with your setup since this is fixed out of the box by Spring Native for a long time. In the meantime, you can follow https://github.com/oracle/graal/issues/4489...

Indeed I see the error: ``` org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'job': Unsatisfied dependency expressed through method 'job' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name...

Hum, your PR seems to break the AOT mode on the JVM as well (tested with `./build.sh -a` on both `main` and `sb-3.0.x` branches). Pinging @snicoll in case this could...

For this kind of use case, we don't have explicit trigger from the annotation based programming model, so 2 potential solutions that I am mentioning here more for discussion related...

FWIW Spring Framework 6 will provide some reusable helper to register the relevant type, not only in `@RequestMapping` context, but also applied to other ones.

@mzhafez For Maven with your commit cherry-picked on top on `main` I can't reproduce. Could you try again rebased on top of `main` after doing a `mvn install` or `build.sh`...

@mzhafez Could you please check your project is working on native in a single module fashion?

I made various changes and tries locally, they seems to show that module dependency like `api project(':core')` are not taken in account during native builds, if I use `implementation 'com.example:core:0.0.2-SNAPSHOT'`...