Re: license question?
From: Byron A Jeff (byron_at_cc.gatech.edu)
Date: 10/15/04
- Next message: Byron A Jeff: "Re: license question?"
- Previous message: xarax: "Re: license question?"
- In reply to: Todd Knarr: "Re: license question?"
- Next in thread: Peter: "Re: license question?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 15 Oct 2004 09:54:06 -0400
In article <Gepbd.73478$a85.55372@fed1read04>,
Todd Knarr <tknarr@silverglass.org> wrote:
-In comp.os.linux.misc <a52de42d.0410131813.6c46b5b3@posting.google.com> Peter <cmk128@hotmail.com> wrote:
-> In my java program, i called some function from another jar
-> file(GPL). And i will include that GPL jar file into my jar file. It
-> is a static link or dynamic link?
-
-In Java, it would probably be considered a static link. Your jar
-file physically contains GPL'd code, it either has to be distributed
-under the terms of the GPL or you are violating the copyright on
-the GPL'd code by distributing copies without a valid license.
-
-Fortunately, with Java you don't need to even worry about this. Java
-can load classes without having them physically within the application's
-jar file. Just distribute the GPL'd jar alongside your code but
-not physically included within your jar files, install the GPL'd jar
-files into a directory in the CLASSPATH and Java should happily find
-and load them when you use them. Since they're physically seperate
-from your program you can distribute your code under any terms you
-want without interfering with distributing the GPL'd code under the
-terms of the GPL. IIRC Java doesn't do header files the way C does
-#include'd headers, so there's not the issue of header code being
-physically included in your classes that makes the GPL-vs-LGPL
-distinction important for C programmers and others.
I agree with you wholeheartedly if we were talking about the LGPL.
But with the GPL it's more dicey. If at any point in the process the
two components share address space, names, or the like then it's
possible that the resulting executable is deriviative thus subjecting
the proprietary jar.
You need to ask the author of the GPL jar about the intent of use.
Frankly this discussion gets really old. I just don't see why
proprietary developers can't understand the underlaying intent.
When someone slaps a GPL license on some code: THEY DON'T WANT YOU
TO USE THAT CODE WITH PROPRIETARY CLOSED SOURCE! Because if they
did there are a zillion other licenses that they could have used
instead, like the LGPL, BSD, ZPL, Artistic, or wxWindows library
licenses for example. GPL markes the code for use in Open Source
only projects.
The answer to the nieve question "Can I combine my proprietary
closed source to GPL code?" should be a flat NO!
I just wish folks would stop string to put that square peg in the
round hole. In the end it doesn't fit.
BAJ
- Next message: Byron A Jeff: "Re: license question?"
- Previous message: xarax: "Re: license question?"
- In reply to: Todd Knarr: "Re: license question?"
- Next in thread: Peter: "Re: license question?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|