4 ms·
Like the other poster, we have to compile it separately on different architecture machines (we are on Bitbucket). We use Quarkus as the base and picocli as the
by killingtime74 2y ago
Like the other poster, we have to compile it separately on different architecture machines (we are on Bitbucket). We use Quarkus as the base and picocli as the cli https://quarkus.io/guides/picocli https://quarkus.io/guides/picocli. Quarkus takes care of a lot and makes the native image experience nicer. Size wise, for internal use our users don't complain, since we are all devs.
I think you can shrink the size with one of the optimisation levels https://www.graalvm.org/latest/reference-manual/native-image/optimizations-and-performance/#optimization-levels https://www.graalvm.org/latest/reference-manual/native-image...