You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GNU General Public License v3.0 imposes conditions on any software integrating a GPL license artifact which are rarely compatible with commercial software.
Switching to LGPL (GNU Lesser General Public License) would broaden the number of projects in which this library can be used.
The text was updated successfully, but these errors were encountered:
Thanks for raising this issue. The licensing is twofold in this case. If you want to integrate or modify the source code, you need to conform to GPL. If you just want to use the binary artifact (as published on Maven Central) as is, an Apache license applies.
Maybe I can make the conditions more clear by removing the GPL source code license. The Choose an open source license project provides a lot of useful information on that topic. I will give it some thought...
The GNU General Public License v3.0 imposes conditions on any software integrating a GPL license artifact which are rarely compatible with commercial software.
Switching to LGPL (GNU Lesser General Public License) would broaden the number of projects in which this library can be used.
The text was updated successfully, but these errors were encountered: