[
https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292535#comment-17292535
]
Aleksandar Vidakovic commented on FINERACT-982:
-----------------------------------------------
[~kaze] the new mechanics in FINERACT-1177 are very simple: you just drop your
driver jars let's say in a folder "libs" next to your fineract-provider.jar and
provide an additional startup parameter "" that points to the folder with your
JDBC driver jars. That way those drivers that are license incompatible can
easily be added to the Fineract's classpath without manually extracting the
Spring Boot uber-jar (as it was done before e. g. in the Docker image build).
And then obviously you just have to change the driver class name and JDBC
connection string in your configuration.
So it should be fairly easy - once FINERACT-1177 gets accepted - to use any
Mysql driver (Drizzle, MariaDB, Mysql Connector Java) as the standard driver in
tests, because the driver is technically not part of the distribution (i. e. we
are still compliant with the Apache License constraints).
> Completely ditch use of Drizzle JDBC Driver after all
> -----------------------------------------------------
>
> Key: FINERACT-982
> URL: https://issues.apache.org/jira/browse/FINERACT-982
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Assignee: Yemdjih Kaze Nasser
> Priority: Blocker
> Labels: scalability
> Fix For: 1.5.0
>
>
> 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...
> FYI [~awasum], [~ptuomola], [~xurror]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
