Open Source Stack Exchange is a question and answer site for people organizing, marketing or licensing open source development projects. It only takes a minute to sign up.
Sign up to join this community
I have found a Java library that can be used under the GPL licence (not the LGPL licence).
Can I embed the library in my program without the requirement of using the GPL licence?
Essentially I believe this is a question about if this a derivative work, or independent work with another component.
Yes, your program must also be GPL.
GPL is quite clear on this matter: if your program links to a GPL library, no matter the type of linking, then your program also comes under the GPL (when you distribute). LGPL adds a dynamic linking exception, but this doesn't apply in your case.
With Java it's no different; if your program links with a GPL .jar, it is considered a derivative as far as the GPL is concerned. LGPL also works as intended with Java.
The typical arrangement for Java is that each library an application uses is distributed as a separate JAR (Java Archive) file. Applications use Java's “import” functionality to access classes from these libraries. When the application is compiled, function signatures are checked against the library, creating a link. The application is then generally a derivative work of the library. So, the copyright holder for the library must authorize distribution of the work. The LGPL permits this distribution.
So in your Java project, if it ever includes a .jar that is GPL, or you type in "import foobar" where foobar is GPL, then your program is also affected.
Absolutely yes. The GPL is very strict on this: any type of (code) linking to a GPL-licensed library is considered derivative and must also come under GPL. In Java, this means a single import statement can change your licensing options. In C#, if you use a GPL library, you must choose the GPL.
It's not clear whether this only applies to code or any library that helped you out. Technically, if you stared developing based off some GPL code then your work is a derivative even if you replace every bit of the original code. (Of course, nobody'll know in this case, but morals? No?)
Worth also noting that the LGPL (linkable GPL) is more lax: you can dynamically link a library and keep your license. This includes DLLs and external JARs for Java.
