You’re basically running into the same sort of problem as this topic: Dealing with plugin classpath conflicts and Classpath / classloader conflicts with other plugins in the buildscript
The issue here is the dependency comes through gradleApi() and there’s not a way to override it. We include a log4j-over-slf4j dependency that contains those same classes.
For your particular case, I think it might make sense to make your Soap related tasks JavaExec’s and fork a separate process rather than run that code within the Gradle process.