jsch dependencySubstitution no longer works in Gradle? about jsch HOT 7 CLOSED

well this is not really a problem of jsch...
I started simple gradle setup with --scan
As you can see on https://scans.gradle.com/s/kzlgphskuyd7e/build-dependencies/repositories the build dependencies contain the substituted jar, so I guess it's just a bug in the buildenvironment task.

Also

task printJschVersion() {
    println("jsch version = " + com.jcraft.jsch.JSch.VERSION)
}

gives:

$ gradlew wrapper --gradle-version 8.5
$ gradlew -q printJschVersion
jsch version = 0.2.4

from jsch.

btw you can also substitute the com.jcraft:jsch.agentproxy and com.jcraft:jzlib with com.github.mwiede:jsch:0.2.14 because these have been included in the main jar.

from jsch.

Does also substituting in agentproxy and jzlib provide any improvements besides possibly just removing any remaining dependency on the com.jcraft jar? thanks

from jsch.

Hi @am312,

It's possible it could cause issues if the older implementations somehow are utilized instead of our built-in versions.
We would highly encourage you to remove them.

Thanks,
Jeremy

from jsch.

Hi @norrisjeremy.
So you'd suggest something like this?

buildscript {
  dependencies {
    classpath "pl.allegro.tech.build:axion-release-plugin:1.14.2"
  }

  configurations.all {
    resolutionStrategy.dependencySubstitution {
      substitute module("com.jcraft:jsch") using module("com.github.mwiede:jsch:0.2.14") because "jcraft jsch is unmaintained"
      substitute module("com.jcraft:jsch.agentproxy") using module("com.github.mwiede:jsch:0.2.14") because "jcraft jsch is unmaintained"
      substitute module("com.jcraft:jzlib") using module("com.github.mwiede:jsch:0.2.14") because "jcraft jsch is unmaintained"
    }
  }
}

Thanks
-Andrew

from jsch.

Hi @am312,

I'm not especially familiar with gradle, so I'm unsure exactly how it would be accomplished.
Perhaps @mwiede is more familiar and can comment?

Thanks,
Jeremy

from jsch.

@am312 yes the substitutions you made look ok to me

from jsch.