-
Type:
Question
-
Status: Resolved
-
Priority:
Major
-
Resolution: Information Provided
-
Component/s: None
-
Labels:None
Dear Apache Legal Affairs Committee,
I am aware that use of LGPL libraries are "frowned upon" for Apache.org hosted ASL projects.
The Fineract Community is running into the specific issue FINERACT-761 we'd welcome your view on:
We need to use a JDBC driver to connect to the MariaDB (or MySQL) database. The BSD 3-Clause licensed https://github.com/krummas/DrizzleJDBC appears to be dead and unmaintained for over 3 years. Its current use in Fineract is causing us pain, see FINERACT-761 req. for FINERACT-700 (also note e.g. https://github.com/flyway/flyway/issues/2332).
The altnerative is the MariaDB.org Connector/J JDBC driver from https://downloads.mariadb.org/connector-java, which is LGPL.
What is a project supposed to do in a case like this? Or are we seriously saying that Apache.org (Java) projects basically can't really use MariaDB (or MySQL) in practice?
How do other Java based projects at Apache.org which use MariaDB (or MySQL) deal with this conundrum??
Would it be legally OK to use the MariaDB.org Connector/J JDBC driver at least during build time in Gradle for Flyway, if it is not shipped in the final Fineract end-user distribution?
Thank you very much for your help in somehow unblocking this,
M.
PS: Many ASL Java projects not hosted on Apache.org seem to depend on the LGPL MariaDB.org Connector/J, but that's (probably) not relevant to Apache.org and this issue.
- blocks
-
FINERACT-761 Use of (unmaintained) Drizzle JDBC driver in Fineract Build (not run-time) prevents upgrading Flyway <- Gradle
-
- Resolved
-
-
FINERACT-762 Use of (unmaintained) Drizzle JDBC driver in Fineract at run-time (not build) is sub-optimal for performance
-
- Resolved
-
- is related to
-
-
- In Progress
-