Error compiling the project: Duplicate classes about fiskaly-kassensichv-client-java

[auxdevelopment]

Does this occur during the build of the Java client or when building a project that depends on the built client?

When building the project that depends on the built client (Android)

[auxdevelopment]

I'm not sure if we can fix anything about that issue. The duplicate classes come from the OkHttp library and therefore are needed in the fat JAR.

What you could try to do tough is finding a way to exclude duplicate classes during your build. If you're using the java plugin for Gradle then you can set the following value to exclude duplicate classes from your build:

jar {
    duplicatesStrategy = 'exclude'
}

I asked the question on Stackoverflow :
https://stackoverflow.com/questions/58557320/android-how-to-exclude-duplicate-classes-while-importing-a-fat-jar

I'm crossing my fingers to get an answer because I'm really stuck with this problem.

[prempador]

@Greelings After a bit of research I found out about packagingOptions:

From here it reads:
Packaging options are configured with three sets of paths: first-picks, merges and excludes:

First-pick
Paths that match a first-pick pattern will be selected into the APK. If more than one path matches the first-pick, only the first found will be selected.
Merge
Paths that match a merge pattern will be concatenated and merged into the APK. When merging two files, a newline will be appended to the end of the first file, if it doesn't end with a newline already. This is done for all files, regardless of the type of contents.
Exclude
Paths that match an exclude pattern will not be included in the APK.

I don't know if this is any help or a solution for you.

Other things I thought about is using our Modules in the repo and adding those with the needed dependencies into your jar instead of using the fat jar we generate.

Hope this can help you somehow.

Thank you.

Other things I thought about is using our Modules in the repo and adding those with the needed dependencies into your jar instead of using the fat jar we generate.

Yes I thought about it too. Because it was working well with earlier versions of the JAR file, imported like this:

implementation files('libs/com.fiskaly.kassensichv.client.android-0.0.1-alpha.jar')
implementation 'com.squareup.okhttp3:okhttp:4.0.1'
implementation 'com.fasterxml.jackson.core:jackson-databind:2.9.9'

I tried to find a simple solution all day yesterday, but without success.
I will continue to use the old JAR file I have to be able to continue the integration, praying for you to return to a classic dependency system (at least for Android).

[prempador]

There will be more changes to the dependency systems in the next few days / weeks. Hopefully this will fix the issues in the future.

@prempador Perfect, thank you. Let me know when you have some news.