missionary

2024-10-29T20:06:53.039099Z

Hi! I am using missionary in app that have to be compiled into GraalVM native image. I found out that for now it works with such initialize time properties:

"--initialize-at-build-time"
"--initialize-at-run-time=missionary.core.,missionary.impl."
"--initialize-at-build-time=missionary.impl.Propagator$Publisher"
But I guess that such settings are exactly for my particular case. Maybe you can suggest more generic approach?

leonoel 2024-10-30T19:48:59.260379Z

I filed an issue - https://github.com/leonoel/missionary/issues/123 I'm interested in official support for GraalVM, your contribution is welcome

👍 1
leonoel 2024-10-29T21:15:15.639179Z

I never used graalvm. Do you know why Propagator$Publisher needs special treatment ? Is it because it's a nested class ?

2024-10-29T22:24:10.300379Z

GraalVM's native-image just suggested me such config change about Propogator$Publisher after build fails. Looks like need to do further investigation.

2024-10-29T22:39:52.557949Z

I guess it is because static initialisation block

static {
    Util.printDefault(Publisher.class);
}
that modifying printDefault method inside. Such behaviour unacceptable in runtime of GraalVM native image