FINERACT-810 Upgrade Flyway version

[percyashu]

Description

Upgrade Flyway to latest spring boot compatible version
https://issues.apache.org/jira/browse/FINERACT-810

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

• Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

• API documentation at https://github.com/apache/fineract/blob/develop/api-docs/apiLive.htm has been updated with details of any API changes.

• Integration tests have been created/updated for verifying the changes made.

• All Integrations tests are passing with the new commits.

• Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

[percyashu]

@awasum or @vorburger I need some help with this issue.

[percyashu]

@awasum and @vorburger, I don't know why MySQL 0.1 is the version used.
I found out that the upgraded Flyway does not support outdated MySQL 0.1 when using Drizzle driver and currently supports MySQL 5.1 and newer.

[percyashu]

I have been doing some research.
I found out from flyway/flyway#2332 that Flyway support only the official MySQL driver.
Drizzle JDBC driver is incompatible with current Flyway version. I was thinking on changing the drizzle driver to MySQL connector or MariaDB ConnectorJ

[vorburger]

I was thinking on changing the drizzle driver to MySQL connector or MariaDB ConnectorJ

unfortunately we cannot, due to licensing issues; look at my comment from June 11 in flyway/flyway#2332 which you found... in theory, the best way to get out of this impasse would probably be to contribute a fix to Flyway (an active project) or krummas/DrizzleJDBC#46 (dead project?).

If we cannot do that (anyone reading this interested?), then perhaps we should just give up on this.

[percyashu]

the best way to get out of this impasse would probably be to contribute a fix to Flyway (an active project) or krummas/DrizzleJDBC#46 (dead project?).
If we cannot do that (anyone reading this interested?), then perhaps we should just give up on this.

I think the issue lies with the https://github.com/krummas/DrizzleJDBC and since it has been inactive for a while now we should just give up on it.

[vorburger]

The problem is that unfortunately we apparently can't use that other MySQL JDBC driver, due to licensing issues (no LGPL at ASF).

[github-actions]

This pull request seems to be stale. Are you still planning to work on it? We will automatically close it in 30 days.

[nemux]

the best way to get out of this impasse would probably be to contribute a fix to Flyway (an active project) or krummas/DrizzleJDBC#46 (dead project?).
If we cannot do that (anyone reading this interested?), then perhaps we should just give up on this.

I think the issue lies with the https://github.com/krummas/DrizzleJDBC and since it has been inactive for a while now we should just give up on it.

That is true @percyashu, I already submited a patch for Drizzle in krummas/DrizzleJDBC#48.

With this research I did other pull request in OpenJPA in apache/openjpa@26b1f6b which is now merged.

With this patched version I was able to run fineract using even MySQL 8.0.12