graalvm

rafaeldelboni 2022-09-24T13:46:49.298239Z

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

borkdude 2022-09-24T13:51:38.614549Z

@rafaeldelboni -H:Log=registerResource: should work according to https://www.graalvm.org/22.1/reference-manual/native-image/Resources/

rafaeldelboni 2022-09-24T13:59:35.132919Z

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

borkdude 2022-09-24T14:02:00.254339Z

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

rafaeldelboni 2022-09-24T14:03:16.888399Z

True, thanks a lot.

rafaeldelboni 2022-09-24T17:31:49.035179Z

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

borkdude 2022-09-24T18:47:07.097439Z

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

rafaeldelboni 2022-09-24T20:38:35.783499Z

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/

borkdude 2022-09-24T20:39:26.164489Z

ah!

borkdude 2022-09-24T20:39:48.563589Z

Well, TIL. Thanks! :)

rafaeldelboni 2022-09-24T20:40:12.143509Z

Me too 😬

rafaeldelboni 2022-09-24T14:20:31.485729Z

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