Repository navigation
Does the Classpath Exception apply to Web Image generated Wasm/JavaScript output? #14612
Unanswered
AndreasOlausson
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello, and thank you for Web Image.
I’m building a commercial, closed-source desktop application that includes a small Java module compiled to WebAssembly using Web Image from a Community Edition build of this repository, not Oracle GraalVM.
Before releasing the application, I’d like to clarify the license status of the generated output.
The repository README lists Web Image under “GPL 2”, without the Classpath Exception, while the Native Image runtime and compiler are listed as “GPL 2 with Classpath Exception”.
However, every source file under web-image/src that I have checked — 796 of 796 .java and .js files — carries Oracle’s explicit designation:
Oracle designates this particular file as subject to the “Classpath” exception as provided by Oracle in the LICENSE file that accompanied this code.
The web-image/LICENSE file itself contains the Classpath Exception text and states that the exception applies where the relevant file header designates the file accordingly.
The JavaScript runtime emitted alongside the generated .wasm also appears to be assembled from source files carrying the same designation.
I would therefore like to clarify two points:
For context, the remaining code incorporated into the generated output appears to come from:
I’m mainly trying to determine whether the generated .wasm and accompanying JavaScript may be distributed inside a closed-source commercial desktop application without imposing GPL licensing requirements on the application itself.
Thank you for any clarification.
All reactions