• Removed noReflect option (https://youtrack.jetbrains.com/issue/KT-44361)
• Added -Xjvm-default=all-compatibility to make interface default methods compatible (https://kotlinlang.org/docs/java-to-kotlin-interop.html#compatibility-mode-for-default-methods)
• Updated dependency versions (there was some issue I couldn't understand with updating gradlew to 7.4, for now kept it as it is)
• Add versions plugin to get new versions of dependencies

Please let me know if there are any suggestions.

@morazow , thank you for your interest and contributions.

Since technically I am not working for badoo anymore, I am currently not in position to approve or reject changes in badoo organization. What I suggest to do is the following:

1. Fork this repo and play around with it for a few weeks. Make it compatible with latest Kotlin and JVM trends, etc. Fix tests.
2. Make one combined pull request.
3. I'll ping a person who still works for badoo and who will be able to review & approve changes.

Please note, Exasol made a lot of changes in the most recent versions. For example, now the latest protocol version is 3. Exasol SAAS uses OpenID tokens for authentication. Encryption is now enabled by default and it will be mandatory starting from Exasol v8.

It might be worth sticking with JDBC for production-critical workloads. The only real advantage of kexasol is "CSV streaming".

Hey @littleK0i,

Thanks for the update! I have added changes for other two issues, I'll check issues with build.

It would be good to have continued maintenance and release of the library. At the moment, we are going to use it for a connector in enclosed cloud service. As you said we would like to use the CSV features from Java and JVM languages.

I'll discuss with our PM if joint collaboration could be arranged. Thanks a lot for the great work!

Ah, you're from Exasol dev team.

In theory, you may just fork this repo and maintain it in Exasol organization. Since the license is Apache 2.0, no one will object to this.