Fork me on GitHub
#graalvm
<
2022-09-24
>
rafaeldelboni13:09:49

Is there any way to debug/check the files being included by -H:IncludeResources ?

rafaeldelboni13:09:35

strange it only shows classes, not the files like config or sql.

borkdude14:09:00

Yeah, I've noticed this too. Perhaps you can post this question in the graalvm community slack native image channel

rafaeldelboni14:09:16

True, thanks a lot.

rafaeldelboni17:09:49

Adding the reply from graalvm slack channel here, about the same question: -H:Log=registerResource:3 This did the trick

borkdude18:09:07

Ah thanks! Where can we find this in the docs?

rafaeldelboni20:09:35

I just found this: > To see which resources are included in the native executable, use the option -H:Log=registerResource:<log level>. The <log level> must be in the range from 1 to 5, from least detailed to most detailed. > https://www.graalvm.org/22.0/reference-manual/native-image/Resources/

borkdude20:09:48

Well, TIL. Thanks! :)

rafaeldelboni20:09:12

Me too 😬

rafaeldelboni14:09:31

Hey btw, I just finished rewriting my microservice boilerplate with libs that are "GraalVM friendly" It's far from perfect and I had to rewrite a lot of stuff like interceptors for request/response body parsing, but is working now. It features config/env parsing, logs, database migration, HTTP requests and etc. https://github.com/rafaeldelboni/microservice-boilerplate-graalvm The "downside" is the size of the compiled bin that is 89mb vs 35mb from the uberjar. Anyway I would love some feedback.

🚀 1