Dependency Conflicts With New Version 2.1.5

[mattiabellohorsa]

After i upgrade the version of dependency at 2.1.5, i see that error: Executing tasks: [:app:assembleSonocoDebug] in project C:\Users\mattia.bello\Documents\Projects\InventoryScanner-Android\InventoryScanner

Task :app:preBuild UP-TO-DATE Task :app:preSonocoDebugBuild UP-TO-DATE Task :app:compileSonocoDebugAidl NO-SOURCE Task :app:writeSonocoDebugApplicationId UP-TO-DATE Task :app:compileSonocoDebugRenderscript NO-SOURCE Task :app:generateSafeArgsSonocoDebug UP-TO-DATE Task :app:generateSonocoDebugBuildConfig UP-TO-DATE Task :app:prepareLintJar UP-TO-DATE Task :app:prepareLintJarForPublish UP-TO-DATE Task :app:generateSonocoDebugSources UP-TO-DATE Task :app:dataBindingExportBuildInfoSonocoDebug UP-TO-DATE Task :app:dataBindingMergeDependencyArtifactsSonocoDebug UP-TO-DATE Task :app:generateSonocoDebugResValues UP-TO-DATE Task :app:dataBindingMergeGenClassesSonocoDebug UP-TO-DATE Task :app:generateSonocoDebugResources UP-TO-DATE Task :app:mergeSonocoDebugResources UP-TO-DATE Task :app:dataBindingGenBaseClassesSonocoDebug UP-TO-DATE Task :app:dataBindingExportFeaturePackageIdsSonocoDebug UP-TO-DATE Task :app:createSonocoDebugCompatibleScreenManifests UP-TO-DATE Task :app:extractDeepLinksSonocoDebug UP-TO-DATE Task :app:processSonocoDebugManifest Task :app:processSonocoDebugResources Task :app:kaptGenerateStubsSonocoDebugKotlin FAILED

FAILURE: Build failed with an exception.

• What went wrong: Execution failed for task ':app:kaptGenerateStubsSonocoDebugKotlin'.

  Could not resolve all artifacts for configuration ':app:sonocoDebugCompileClasspath'. Failed to transform bcprov-jdk15on-1.66.jar (org.bouncycastle:bcprov-jdk15on:1.66) to match attributes {artifactType=android-classes-jar, org.gradle.category=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-api}. Execution failed for JetifyTransform: C:\Users\mattia.bello.gradle\caches\modules-2\files-2.1\org.bouncycastle\bcprov-jdk15on\1.66\ed564ade61defca27e26fb1378a70b22831fc5c1\bcprov-jdk15on-1.66.jar. Failed to transform 'C:\Users\mattia.bello.gradle\caches\modules-2\files-2.1\org.bouncycastle\bcprov-jdk15on\1.66\ed564ade61defca27e26fb1378a70b22831fc5c1\bcprov-jdk15on-1.66.jar' using Jetifier. Reason: IllegalArgumentException, message: Unsupported class file major version 59. (Run with --stacktrace for more details.) Suggestions:

  • Check out existing issues at https://issuetracker.google.com/issues?q=componentid:460323&s=modified_time:desc, it's possible that this issue has already been filed there.
  • If this issue has not been filed, please report it at https://issuetracker.google.com/issues/new?component=460323 (run with --stacktrace and provide a stack trace if possible).

• Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

• Get more help at https://help.gradle.org

BUILD FAILED in 2s 17 actionable tasks: 3 executed, 14 up-to-date

Then, i try to downgrade at 2.1.4 and my project build without problem.

Why this behavior ?

[mbechler]

This error is due to the new bouncycastle version which is provided as a multi-release JAR which a lot of software unfortunately has problems with. You can work around this by replacing the dependency with bcprov-jdk15to18. This is going to be the case for upcoming versions (but no concrete plans for a release yet).

[axelrindle]

I could fix the issue by changing the following in my app build.gradle:

implementation 'org.bouncycastle:bcprov-jdk15to18:1.66'
implementation (group: 'ch.pontius.nio', name: 'smb-nio', version: '0.8.0') {
    exclude group: 'org.bouncycastle', module: 'bcprov-jdk15on'
}

[mbechler]

Ultimately, you should be able to freely choose between jdk15to18 and jdk15on versions for your projects and override the deps accordingly. Unfortunately this seems to be causing some issues both ways (in your case by pulling both artifacts at the same time, in others with various tools not supporting multi-release JARs), so I guess there is no way around people managing their depencies properly. So far the broken tooling case has come up more often so I think sticking with jdk15to18 makes sense.

[col-panic]

Same happens for bouncycastle 1.68

[michaldo]

Same happens for bouncycastle 1.69

[rastislavpapp]

@mbechler I've encountered this problem with jcifs-ng/2.1.5 running on apache-karaf, after upgrading to a new version (4.3.6) which bumped bouncycastle to 1.69. I've tried upgrading to jcifs-ng/2.1.7, and it solved the issue, somehow :-)

[mbechler]

I switched back to the "regular" bouncycastle (= multi-release JAR) dependency in 2.1.7, as I got the feeling this was causing more issues than the other way round.

[Liberations]

implementation("org.codelibs:jcifs:2.1.34"){ exclude group: 'org.bouncycastle', module: 'bcprov-jdk18on' } implementation 'org.slf4j:slf4j-api:1.7.36' implementation 'org.bouncycastle:bcprov-jdk15to18:1.66'