graalvm-reachability-metadata

This is great, but you should post it to: https://github.com/oracle/graalvm-reachability-metadata ... as a PR, so that, when merged, other users can pull it into their build automatically, merely by looking up from the relevant dependency's maven coordinates. You can also ship this metadata as part of the library artifact itself[1], by placing configurations at the JAR resource path `META-INF/native-image/<group-id>/<artifact-id>/reachability-metadata.json`, etc [1]: https://www.graalvm.org/latest/reference-manual/native-image...

gcj had a lot of problems beyond needing configuration of reflection metadata. It used a full reimplementation of the standard library, and it was never adopted by the wider Java community being largely just Red Hat's strategy for creating a fully open source Java implementation rather than something offering specific benefits to Java developers. In particular people thought it'd lead to faster code, but GCC was never designed for Java and the results were actually a fair bit slower iirc. Native image is quite different. With this new release the compiled images can not only be faster than JIT compiled Java (wow) but also use way less memory and start instantly. At a stroke this is resolving one of the biggest complaints people have always had against JVM languages. And as a consequence you're seeing adoption by the wider community. All t

GraalVM is truly great stuff. GraalVM native compilation helps Java in the data center to avoid being a cost sink and to reduce start-up latency. Oracle needs Java to sell enterprise software. Oracle contributing to OpenJDK may be required for Amazon cooperation (since Amazon is pushing its own JDK build) and probably helps the library ecosystem work towards native compatibility. Native support for reflection (used in many libraries) requires "reachability metadata", maps of reflective API usage, at build time. Anyone can do it, but enterprise requires authoritative sources. Until authoritative reachability metadata covers the transitive graph of library+version dependencies in enterprise software, GraalVM native AOT builds are a PITA. - https://github.com/oracle/graalvm-reachability-metadata - latest release: https://medium.com/graalvm

Also, reflection is supported in AOT mode. The analysis, however, does require reachability metadata in some cases. In the best case, libraries provide and maintain appropriate configuration for this. Reachability metadata can also be shared via https://github.com/oracle/graalvm-reachability-metadata.