You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like ThisBuild / versionScheme := Some("strict") is set in build.sbt which means, according to sbt documentation, that it does not impose any compatibility guarantees between releases.
So, one could stuck in a situation when two independent libraries brings (transitively) two different zstd-jni versions (i.e. v1.5.6-4 and v1.5.6-5) to the classpath. In that case, sbt will error out and the conflict will need to be resolved.
So the question is - is this really necessary to declare versionScheme as strict? Are the patch releases really not compatible with one another?
The text was updated successfully, but these errors were encountered:
Looks like
ThisBuild / versionScheme := Some("strict")
is set inbuild.sbt
which means, according to sbt documentation, that it does not impose any compatibility guarantees between releases.So, one could stuck in a situation when two independent libraries brings (transitively) two different zstd-jni versions (i.e. v1.5.6-4 and v1.5.6-5) to the classpath. In that case, sbt will error out and the conflict will need to be resolved.
So the question is - is this really necessary to declare versionScheme as strict? Are the patch releases really not compatible with one another?
The text was updated successfully, but these errors were encountered: