ormlite-jdbc and ormlite-android can no longer be used together

[dlew]

As I understand it, the recent changes to ORMLite 6.x packages (via shading) the core library.

However, this means that you can no longer use both the JDBC and Android versions side-by-side. This causes compilation issues because the same core classes are included twice.

The reason we do this is because in the main app, we use ormlite-android; but in tests, we use ormlite-jdbc.

[j256]

Huh right. Didn't take that into consideration. I could also release ormlite-jdbc-only or something targets. Let me see if I can get the pom.xml file to handle both...

[dlew]

What was the motivation behind including core in the JAR? You could still write one import statement (in maven/gradle/etc) since it'll get picked up with transitive dependencies.

[j256]

Not everyone is using maven or gradle. I still got somewhat frequent questions about how the core classes weren't on the classpath.

[bparent]

Any updates around this?

[dChunGit]

Hi! I'm just checking in on this to see if we're looking at possible solutions, we're currently blocked on updating to 6.x. Thank you!