Details
-
Improvement
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
Description
Fineract's use of the un-maintained Drizzle JDBC driver continues to cause confusion and pains like FINERACT-980, and note e.g. the proposed removal of the alternative MySQL JDBC driver in https://github.com/apache/fineract/pull/887.
Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and LEGAL-462.
LEGAL-462 has clarified that the Fineract ZIP distribution must include Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and currently (given the confusion inĀ FINERACT-980 apparently do?!) use it for tests.
What if to reduce variability we just removed that old Drizzle JDBC driver after all? We could run our tests using (preferably) the very well maintained MariaDB JDBC driver client (the actual DB server is a totally separate discussion, see FINERACT-896). We would (have to) distribute the ZIP for download without a JDBC driver, and just some documentation inviting users to DL and add one.
But the exact situation about distributing in a Docker container image isn't clear, to me...
Attachments
Issue Links
- Blocked
-
FINERACT-1305 Release Apache Fineract v1.5.0
- Resolved
- blocks
-
FINERACT-1168 Integration Tests failure due to internal server errors should show server side failure stack trace
- Resolved
-
FINERACT-890 Custom slf4j integrated logger for the (optional!) MySQL JDBC driver support in Fineract
- Resolved
- relates to
-
FINERACT-980 bootRun broken due to FlywayDbUpgradeRequiredException: MySQL upgrade required: MySQL 0.1 is outdated and no longer supported by Flyway. Flyway currently supports MySQL 5.1 and newer.
- Resolved
-
FINERACT-761 Use of (unmaintained) Drizzle JDBC driver in Fineract Build (not run-time) prevents upgrading Flyway <- Gradle
- Resolved
-
LEGAL-462 How to use MariaDB (MySQL) in Apache.org (Java) projects, given that the only currently maintained JDBC driver is LGPL?
- Resolved
- links to