3 ms·
If I package my Java app together with OpenJDK JRE then GPL code is bundled in my app and I can use "classpath exemption". If I take OpenJDK JRE, fork it, make
by pulse7 9y ago
If I package my Java app together with OpenJDK JRE then GPL code is bundled in my app and I can use "classpath exemption".
If I take OpenJDK JRE, fork it, make Retropiler out of it and publish it under "GPL plus classpath exception" and then package my Java app together with Retropiler then GPL code is bundled in my app - it is the same as above. Why I am not subject to the classpath exception in this case?
- pulse7 9y agoI checked again: 1) OpenJDK allows you to fork under a) GPLv2 or b) GPLv2 + Classpath Exception (see http://openjdk.java.net/legal/gplv2+ce.html http://openjdk.java.net/legal/gplv2+ce.html, "If you modify this library, you may extend this exception to your version of the library, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version." where library=OpenJDK and exception=Classpath Exception). 2) Android's OpenJDK fork is licensed under GPLv2 + Classpath Exception (see https://android.googlesource.com/platform/libcore/+/master/LICENSE https://android.googlesource.com/platform/libcore/+/master/L...) 3) Retropiler OpenJDK runtime is licensed under GPL only (see https://github.com/retropiler/retropiler https://github.com/retropiler/retropiler, "The Java classes in runtime/ module which were copied from AOSP are licensed as GPL.") They could fork OpenJDK and license it with classpath exception which would allow you to (statically or dynamically) bundle your app with OpenJDK under any license. But since they didn't include the classpath exception your app bundling parts of the Retropiler's OpenJDK fork must be under GPL! So you can use it only for open source projects...