Eclipse Public License

Eclipse Public License
Author Eclipse Foundation
Latest version 1.0
Published February 2004
DFSG compatible Yes[1]
FSF approved Yes[2]
OSI approved Yes[3]
GPL compatible No[2][4]
Copyleft Limited[2]
Linking from code with a different license Yes[5]

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.[6]

The Eclipse Public License is designed to be a business-friendly free software license, and features weaker copyleft provisions than licenses such as the GNU General Public License (GPL).[7] 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.[8]

The EPL is approved by the Open Source Initiative (OSI)[3] and is listed as a free software license by the Free Software Foundation (FSF).[2]

Discussion of a new version of the EPL began in May, 2013.[9]


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.[7] 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.[7] Because this is a "further restriction" on the recipients, distribution of such a combined work does not satisfy the GPL.[2]

The EPL, in addition, does not contain a patent retaliation clause.[2]

Derivative works

According to article 1(b) of the EPL, additions to the original work may be licensed independently, including under a proprietary license, provided such additions are "separate modules of software" and do not constitute a derivative work.[4][8] 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.[8]

Later versions

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.[8]

Comparison with the CPL

The EPL was based on the Common Public License (CPL),[10] but there are some differences between the two licenses:

The Eclipse Foundation sought permission from contributors to re-licence their CPL code under the EPL.[11]

Notable projects

In addition to the Eclipse Foundation, the EPL is used in some other projects, especially those running on the Java virtual machine.

Licensed solely under the EPL

Multi-licensed under the EPL and one or more other licenses

See Also


  1. "Copyright information for Debian package eclipse-emf". Retrieved 2011-02-18.
  2. 1 2 3 4 5 6 "Various Licenses and Comments about Them". Retrieved 2016-06-03.
  3. 1 2 "OSI approval". Retrieved 2007-06-21.
  4. 1 2 "Eclipse Public License (EPL) Frequently Asked Questions". Retrieved 2009-12-18.
  5. 1 2 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."
  6. 1 2 3 "Open Source Software: a legal guide | LawGives". LawGives. Retrieved 2015-09-08.
  7. 1 2 3 4 "Eclipse Public License - v 1.0". Retrieved 2006-09-12.
  8. "Community Review of the Eclipse Public License". 2013-05-31.
  9. "CPL to EPL Transition Plan" (PDF). 2006-09-12.
  10. "CPL To EPL Transition Plan Frequently Asked Questions". Retrieved 21 December 2015.
  13. "jruby/COPYING at master - jruby/jruby". GitHub. 2014-01-01. Retrieved 2014-02-11.

External links

This article is issued from Wikipedia - version of the 11/20/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.