Eclipse Public License 2.0, explained

Weak copyleft EPL-2.0 · EPL-1.0

EPL-2.0 is a weak copyleft at module level: you can combine EPL code with closed-source modules, but changes to the EPL code must be shared under the EPL.

Not legal advice. Read the licence text for the exact terms.

What it allows

  • Use it in commercial products
  • Combine it with separate modules under other licences

What it requires

  • Make the source of changed EPL code available when you distribute it
  • Keep notices
  • Commercial distributors take on defence and indemnification duties towards contributors

When it matters

Shipping an appAllowed; publish changes you made to EPL code.
A hosted service (SaaS)No obligation while you do not distribute the code.
Internal useNo obligation.

Its family: weak copyleft

You can use the library in a closed-source product, but changes to the library's own files (MPL, EPL) or to the library itself (LGPL) must be shared under the same licence. LGPL also expects users to be able to replace the library, which is simple with dynamic linking and harder with static linking or bundling.

Questions

Is EPL-2.0 compatible with GPL?

Only if the author allowed it with a "Secondary License" notice naming GPL-2.0 or later; otherwise they are incompatible.

Other licences

Published ; awaiting review.