Hi. Issue 748 is blocking me from upgrading to th...

# exposed

[Carter]

Hi. Issue 748 is blocking me from upgrading to the 0.20.x series. I know the code change has been merged to master. Is there a regular release schedule planned? No rush, just trying to figure out planning on my end as I’d like to be able to make the version bump to unblock some other code changes I’d like to make.

[tapac]

Hopefully today or tomorrow.

[tapac]

You may try 0.20.3

[Carter]

Thanks, I just gave it a try. It looks like my issue might be something else. I’m still getting a java.lang.IllegalStateException: Can't load implementation for DatabaseConnectionAutoRegistration .

If I roll back to 0.17.7 (and make the changes to dependencies and imports for my objects), then it runs just fine.

I can try to troubleshoot some more on my end, although I’m not clear what might isolate it further just yet.

The initialization is pretty straightforward. I’m just trying to use a SQLite database file. I also tried a h2 database but that didn’t make a difference.

[Carter]

I think I got past the issue. 🎉 Looks like some kind of weird caching in IntelliJ was happening.

[Carter]

So I have some more info on the issue I was seeing. I’m using multiplatform, mostly to force me to avoid JVM only stuff getting hooked deeply into many of my model objects I’m writing although I still run the project on the JVM.

exposed is integrated into a library and it has the core and dao dependencies as api, and sqlite-jdbc and exposed-jdbc as implementation.

The app project uses this library and generally has little direct knowledge of exposed.

It seems that something is going wrong with the transitive dependencies to sqlite-jdbc and exposed-jdbc . If I explicitly add them to the app project’s jvmMain dependencies, then it works. I don’t see why it should fail, because they’re already provided by the db module.

[tapac]

Could you please file an issue to github with little more details of your configuration and gradle dependency graph?

[Carter]

I think I figured out the root cause, which was accidentally applying the multiplatform plugin to my root build.gradle, in addition to my modules. I think deleting that resolved this issue.