It seems that the ... syntax is the trigger here, although it's not obvious in the stacktrace.
Anyway, adding this use-case to the GraalVM configuration training seems to be enough to get the missing bits in the native image, and render the expected result:
The following simple sequence diagrams produces an error when rendering a
png
with your native buildplantuml-linux-amd64-1.2023.10
:See resulting image:
We've detected this issue initially on our internal Kroki server, but it can also be reproduced on
kroki.io
: https://kroki.io/plantuml/png/eNpzyk_StXPMyUxOtVLwSM3Jyedyyk-y0dUFC3Hp6emB-KgqFBLTEzPzkNUBAN4_FTU=It seems that the
...
syntax is the trigger here, although it's not obvious in the stacktrace.Anyway, adding this use-case to the GraalVM configuration training seems to be enough to get the missing bits in the native image, and render the expected result:
A test binary (linux-amd64 only) is available here: https://github.com/thomasgl-orange/plantuml/releases/tag/v1.2023.10-tgl2