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.
solvitur ambulando
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.