I'm developing an application which requires a third party framework which is under an Eclipse Public Licence (EPL). The application is a server-side commercial application which will be running on my servers. The EPL software is distributed as binaries (jar files). I'm only using the packages and am not making any contribution, i.e. not making any changes to the source.
Under EPL I believe I'm not a "Contributor" nor am I making a "Contribution". But if I want to make my software available to be installed at some offsite server I'm having trouble with REQUIREMENTS of EPL:
b.iv - "states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange".
Does this mean that if I where to modify the source code of the 3rd party framework for my own purposes I would need to distribute all of my source code?
EPL is supposed to be commercially friendly but it doesn't seem that way to me.
Using EPL-Licensed Code The Eclipse Public License allows users of the licensed code to: Use the code commercially: The EPL imposes no conditions on using the code in software that's sold commercially except for the aforementioned requirement to extend legal protections to EPL contributors.
Eclipse uses the Eclipse Public License (EPL). The EPL is a commercially friendly license that allows organizations to include Eclipse software in their commercial products, while at the same time asking those who create derivative works of EPL code to contribute back to the community.
The Eclipse Public License (EPL) is a free and open source software license most notably used for the Eclipse IDE and other projects by the Eclipse Foundation. It replaces the Common Public License (CPL) and removes certain terms relating to litigations related to patents.
Yes, the EPL is considered a weak copyleft license. Weak copyleft licenses requires you to disclose your source on source code, but not on binaries and therefore you can compile covered sources with others and distribute the resulting (merged) binaries under the license of your choice.
The way that I understand your question is "If I change part of the framework, do I need to redistribute all of the source code of my application, even the parts that aren't part of the framework?". If that is the proper interpretation of your question, then no, you do not need to distribute all the code of your application.
EPL is a weak copyleft license, however it is a non-viral copyleft so it only applies to the source of what was EPL'ed, not to what you build on top of the EPL project. Thus, it does not require that you distribute the source to your application, only the changes made to the framework itself. The terms of the EPL only apply to the source of the library, not the source of your application. Your application's code will governed by its own license (as you are not redistributing it, ostensibly a simple "I own all the rights to this code" license).
Basically, as long as you are not using a library governed by a fully copyleft license, then you should be fine.
Disclaimer: I am not a lawyer. Do not take this as real legal advice.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With