mySql connector license
Posted by: Danijel Jevtic
Date: July 29, 2005 04:29AM

Hello everyone,
I hope that there are some people out there who can clarify this licensing question for me.
Until now I have been programming a web application which is based only on libraries using the Apache License.
I have played a little with the mysql connector/J and find it to be one of the best tools for persisting my data. As of today I have not used any LGPL based software, because of some irregularities in the license. I want to distribute my web app under a commercial license, but think that as soon as I use an LGPL based library I also have to distribute my web app under LGPL.

My believe is strengthened by the following article of the LGPL:
A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.

Since my web app is using an LGPL library it therefore also needs to be LGPL.
Is this correct?

I would appreciate some hints of other users, who may have encountered the same problem. In the future I will be using connector/J 3, but for now I am planning to use connector/J 2, if licensing allows me to do that.
Is there a commercial connector/J 2 or connector/J 3 license which I may not be aware of?
What's may be the difference in the licenses of the two versions?
Any help would be great. Thanks in advance.

Options: ReplyQuote


Subject
Written By
Posted
mySql connector license
July 29, 2005 04:29AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.