I'm developing a java app with my hands and feet. I intend to share it with people and it may become commercial.

He who knows can write it all down in notepad but I have been using Eclipse.

The first thing Eclipse did without me understanding what it did exactly was when I updated the "build path" to add a non standard java library.

This library is from LGPL licenses domain. The Eclipse license EPL and LGPL exclude each other.

What does this mean exactly and how can I get around the EPL license?

I understand you can add a new library to a project as a new dependency within a framework such as Maven or Spring but i'm not yet familiar with how and why to do this.

  • 1
    When you say "I have been using Eclipse", do you mean that you have been using Eclipse's Java IDE to develop your code? – MadHatter Feb 15 '17 at 9:33
  • Yes. Eclipse IDE for Java EE developers – Nikica Feb 15 '17 at 12:45
  • 1
    Why do you think you are bound by the EPL? – MadHatter Feb 15 '17 at 12:53
  • 1
    I can see why you're bound by the LGPL, as your app is linked to a library that's available under that licence. What I don't get, and what I'll ask again, is why you think you're bound by the EPL. If you were contributing to Eclipse, you'd need to contribute code that could be bound by the EPL (which would preclude this LGPL-linked code), but you haven't said you're doing that. You're not bound by the EPL just because you use an EPLed IDE to edit your code, any more than code compiled by gcc is automatically GPLed. Have I missed something? – MadHatter Feb 15 '17 at 18:39
  • 2
    Even if you have included the library, that only explains why you're bound by the LGPL. Why do you think the EPL has any bearing on your code at all? – MadHatter Feb 15 '17 at 20:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.