Discuss GraalVM related topics. Use clojure 1.10.2 or newer for all new projects. Contribute to and GraalVM slack:
kulminaator 2020-01-19T20:22:39.001Z

does someone have a link to graalvm's native-image licensing explained for mere mortals ? 🙂


may be you've seen it already, but fwiw: the first question at: touches a bit on native-image

kulminaator 2020-01-19T20:55:42.002800Z

i know the question and "answer" is there

kulminaator 2020-01-19T20:55:56.003200Z

but i'm really awful at lawyering

kulminaator 2020-01-19T20:56:08.003500Z

that's why i was interested if someone has a human translation

kulminaator 2020-01-19T20:59:01.005Z

i see "graalvm community edition" , but in no sentence anywhere are they actually mentioning the licensing terms for native-image on top of the community edition. all the native-image license talk is related with the graalvm enterprise.

borkdude 2020-01-19T21:05:16.005600Z

@kulminaator you can talk to the graalvm / native-image devs on the GraalVM slack as well

kulminaator 2020-01-19T21:17:03.006Z

i'm pretty sure somone has addressed the question already and has explained it


@kulminaator does this help at all?


fwiw, there are other issues that look like they might have some relevant bits:



re: classpath exception -


note the comment under the answer with score 71:

IANAL, but I am one of the creators of the Classpath Exception, and this is the right answer. The Exception was created to support AOT compiled embedded use cases where developers would be statically linking binaries (with gcj in our case). We needed something like the libgcc license, so I wrote the first version of the Classpath Exception based on that. It has since matured, but the spirit is the same.