[ https://issues.apache.org/jira/browse/FINCN-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955335#comment-16955335 ]
Isaac Kamga commented on FINCN-26: ---------------------------------- [~vorburger] I've eliminated traces of MariaDB from data-jpa, anubis, idenity, permitted-feign-client, provisioner and demo-server. Based on your recommendation, the fineract-cn-mariadb repository can now be safely archived. With that, I'll close this issue. > Replace MariaDB driver with drizzle as JDBC driver > -------------------------------------------------- > > Key: FINCN-26 > URL: https://issues.apache.org/jira/browse/FINCN-26 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-mariadb > Reporter: Myrle Krantz > Assignee: Isaac Kamga > Priority: Blocker > > Fineract CN currently depends on 'org.mariadb.jdbc:mariadb-java-client:1.4.3' > as our JDBC driver. It's for our connection to an SQL database, and can be > used for MySQL as well as MariaDB. This component is licensed as LGPL, and > therefore, needs to be replaced before we release. The current suggestion is > to replace it with drizzle. Other suggestions are also welcome. > Why can't we have dependencies to LGPL software? This sequence of events > would be bad: > 1.) We include LGPL software in our release. > 2.) Our code, including the LGPL dependency is included in proprietary code > of CompanyOmega > 3.) Some judge somewhere decides that the "firewall" separating our code from > the LGPL isn't strong enough to call prevent the viral aspects of LGPL from > taking effect. > 4.) CompanyOmega's proprietary code is now all open source and they go out of > business. > It's not a likely sequence, but because of the size of the negative outcome, > we avoid it by not including LGPL (or any other Category X software) in our > releases. -- This message was sent by Atlassian Jira (v8.3.4#803005)