License question

[geometer]

Please clarify whether the LGPL applies equally to both Java and C++ code. For the C++ part, that's okay, but applying the LGPL to Java code raises concerns for Android apps. Specifically, using an LGPL Java library might require opening the app's source code, as users cannot replace the Java library within an Android app. However, they could still replace the native C++ part.

Does this interpretation imply that using an LGPL Java library in a closed-source Android app would violate the LGPL? Or am I misunderstanding something?

[omicronapps]

This library is an Android port of the 7-zip Java wrapper 7-Zip-JBinding, with only the minimum amount of modifications made to allow it to load and run on Android systems. As this library is based on an existing LGPL licensed project, the license terms that were defined for 7-Zip-JBinding also apply equally to this library.

The license terms are defined on the GitHub page for 7-Zip-JBinding as follows:
https://github.com/borisbrodski/sevenzipjbinding

---------------

7-Zip-JBinding and 7-Zip/p7zip binaries are licensed under GNU LGPL.
For more information about 7-Zip source code licenses please see
7-Zip read me file. For more information about p7zip source code
please see p7zip read me file.```

However, I'm afraid I can't answer to legal implications of using an LGPL licensed Java library in a closed-source Android application.

[geometer]

Thank you. I understand your intention, and of course, you must keep the LGPL for the C++ part of your bindings. However, I’d like to suggest that you consider licensing the Java part under a different, less restrictive license. This approach would not violate the LGPL but allow broader usage of your bindings in closed-source Android applications.

I suspect there may already be applications using your library in ways that violate the license. For those of us who are careful to comply with open-source licenses, this presents an obstacle to using your library.

The LGPL requires end-users to be able to replace the library binary in the application. The common solution is to link the library dynamically, allowing LGPL-licensed libraries to be used in closed-source applications. However, Android does not support a “dynamically linked Java library,” making it impossible to use your library in compliance with the LGPL, although the C++ library can be replaced.

I fully respect whatever decision you make, but I would appreciate it if you could investigate the problem and weaken the license for the Java code.

Anyway, thank you for your work.

[geometer]

Ah, I caught it. Your code is based on another project, and Java code is also LGPL'd in that project. That means I have to address my suggestion to the author of that project. I will do so.