@Dave Fisher I meant the pulsar-client Java package, so that I can compile my application with GraalVM.
Right now, using pulsar in a Java service means paying the full cost of the JVM for each replica of that service. A tiny service that would use 1% cpu and 10mb of memory with native image, uses 5-10% and at least 150mb of memory using JVM, so multipled by many replicas this really adds up. Not to mention the startup time, etc... I did give it a go myself, but unfortunately I am not that proficient with Pulsar internals or GraalVM, so gave up after a while...