In case there’s still any confusion:
usage via importing or subclassing of classes in an lgpl jar DOES NOT create a derivative of the lgpl jar that requires the application/library using the lgpl jar to be released under the LGPL.
About Gunnar
I'm the Chief Technology Strategist for the Red Hat US Public Sector group, an open source and free culture advocate, a picky drinker, an amateur aesthete, and a dog enthusiast.
more...Part of the Commons
onepeople.org by Gunnar Hellekson is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.