Skip to main content

SPL versus LGPL

2 replies [Last post]
Joined: 2003-06-11


I work on a project that is based on NetBeans platform. I thought I might use some of the JDNC components (table and tree table). But LGPL effectivelly stops me from several things:

1. In order to use JDNC I would have to use all of it packed in the original jar (true?). (this is at least according to our legal dept.)
2. I am unable to host it on site as source code, only in so called scrambled binary form (ouch).
3. I would not be able to do any modifications - I would have to contribute patches to this project and wait for them to be included or rejected (true?)

All in all it seems that I will have to live without JDNC components since the legal barrier(s) seems higher than I am able to deal with.

I know this is a bit silly question but what about publishing JDNC components under SPL (Sun Public License)? You may call me a dreamer ...

Thanks for any comments, suggestions etc.,

David Strupl

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2006-02-17

I believe (tho IANAL) that #3 is false. Nothing in the LGPL prevents you from making and distributing changes: it simply imposes the requirement that if you do make changes and distribute the result, you must include or offer to ship the source, including the source for your changes.

If you can't distribute source, then you can't distribute the binary or any derivitives.

It seems unusual to me that (ie, a fairly open source project itself) would prohibit you from posting the source to a dependant library. If this is truly the case, then consider creating a project on sourceforge, codehaus, freshmeat, or any of the other opensource distribution points: you can (and in fact are usually required to) distribute source from there. Note that this doesn't imply that you have to create a mirror and track changes: you simply have to include the source upon which you built (easiest way is to simply include the source in a .zip file and be done with it).

Dave Hall

Joined: 2003-06-11

You are right - my #3 is indeed wrong. Using some other open source distribution site (SourceForge) is a good suggestion and I will consider it. Thanks.

As for it accepts only SPL (Sun Public License) code contributions -

David Strupl