Eclipse Public License
|Linking from code with a different license||Yes|
The Eclipse Public License (EPL) is an open source software license used by the Eclipse Foundation for its software. It replaces the Common Public License (CPL) and removes certain terms relating to litigations related to patents.
The Eclipse Public License is designed to be a business-friendly free software license and features weaker copyleft provisions than contemporary licenses such as the GNU General Public License (GPL). The receiver of EPL-licensed programs can use, modify, copy and distribute the work and modified versions, in some cases being obligated to release their own changes.
Discussion of a new version of the EPL began in May, 2013.
The EPL 1.0 is not compatible with the GPL, and a work created by combining a work licensed under the GPL with a work licensed under the EPL cannot be lawfully distributed. The GPL requires that "[any distributed work] that ... contains or is derived from the [GPL-licensed] Program ... be licensed as a whole ... under the terms of [the GPL]", and that the distributor not "impose any further restrictions on the recipients' exercise of the rights granted". The EPL, however, requires that anyone distributing the work grant every recipient a license to any patents that they might hold that cover the modifications they have made. Because this is a "further restriction" on the recipients, distribution of such a combined work does not satisfy the GPL.
According to article 1(b) of the EPL, additions to the original work may be licensed independently, including under a commercial license, provided such additions are "separate modules of software" and do not constitute a derivative work. Changes and additions which do constitute a derivative work must be licensed under the same terms and conditions of the EPL, which includes the requirement to make source code available.
If a new version of the EPL is published the user/contributor can choose to distribute the software under the version with which he or she received it or upgrade to the new version.
Comparison with the CPL
- The Eclipse Foundation replaces IBM as the Agreement Steward in the EPL
- The EPL patent clause is revised by deleting the sentence from section 7 of the CPL
A clause contained within the CPL allows for developers to migrate software under the terms of the CPL to the terms of the EPL at any time, similar to how users of the GPL version 2 can migrate to the GPL version 3.
Projects using the EPL
In addition to the Eclipse Foundation, the EPL is used in some other projects, especially but not limited to those running on the Java virtual machine. Symbian, Graphviz, Clojure, Mondrian OLAP server, Open Daylight Project and UWIN all have their source code released under the EPL. JRuby is currently tri-licensed under the terms of the EPL, the GPL, and the LGPL.
- "Copyright information for Debian package eclipse-emf". Retrieved 2011-02-18.
- "Various Licenses and Comments about Them". Retrieved 2006-09-20.
- "OSI approval". Retrieved 2007-06-21.
- "Eclipse Public License (EPL) Frequently Asked Questions". Retrieved 2009-12-18.
- In section 7, this sentence is in CPL 1.0, but not EPL 1.0: "If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed."
- "Eclipse Public License - v 1.0". Retrieved 2006-09-12.
- "Community Review of the Eclipse Public License". 2013-05-31.
- "CPL to EPL Transition Plan". 2006-09-12.
- "jruby/COPYING at master - jruby/jruby". GitHub. 2014-01-01. Retrieved 2014-02-11.