Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Q: Should this library really declare a strict versionScheme? #325

Open
olegbonar opened this issue Sep 11, 2024 · 0 comments
Open

Q: Should this library really declare a strict versionScheme? #325

olegbonar opened this issue Sep 11, 2024 · 0 comments

Comments

@olegbonar
Copy link

olegbonar commented Sep 11, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant