Support Java 11 or later

[komamitsu]

This PR fixes #29.

The current implementation tries to cast jdk.internal.loader.ClassLoaders$AppClassLoader to java.net.URLClassLoader. It works in Java 8, but doesn't work in Java 11 or later since ClassLoaders$AppClassLoader no longer inherit java.net.URLClassLoader.

The PR also upgrades the version of Guice since version 4 doesn't work with Java 17 or later.

I confirmed if this change works as follows:

• ./gradlew installDist in the Kelpie project directory using Java 8
• Clone https://github.com/scalar-labs/scalardb-benchmarks, build a shadow Jar using Java, and execute the Kelpie Jar built above with 8, 11, 17 and 21

[yito88]

Thank you! Can we test Kelpie with all Java versions we support in the CI?

kelpie/.github/workflows/kelpie.yaml

Line 23 in 05dc78a

java-version: 1.8

[komamitsu]

@yito88 I'm okay to update the workflow file to execute ./gradlew build with multiple Java versions. But I'm not sure if it makes sense, because:

• It seems Kelpie has only com.scalar.kelpie.config.ConfigTest. The original issue occurs when com.scalar.kelpie.modules.ModuleLoader#loadModule is evaluated. So, executing ConfigTest even with multiple Java versions doesn't guarantee Kelpie works in Java 11 or later.
• The original issue occurs when com.scalar.kelpie.modules.ModuleLoader#loadModule is evaluated in Java 11 or later. So, I guess simple unit tests won't be enough. Probably we should add integration tests which builds a Jar file and executes it via Kelpie executable somehow.

What do you think?

[yito88]

Right, we could add some integration tests. How about running small ones with scalar-labs/kelpie-test in the CI?

[yito88]

The CI stuff could be separated from this PR

[komamitsu]

@yito88 Thanks for the suggestion! It sounds good. I'll try it when I have a time later.

[brfrn169]

LGTM! Thank you!

[feeblefakie]

LGTM! Thank you!