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
It is common for real-world applications to have several versions of scala-logging in their dependency graphs, which leads to sbt giving eviction warnings.
I couldn't find a documented versioning policy, so I'm not sure when I should be worried. sbt now offers a more formal way than documentation, in the versionScheme setting that libraries can declare. It'd be great if scala-logging's build/artifacts include this.
Perhaps sbt-version-policy, or MiMa alone, can be employed to keep us honest.
The text was updated successfully, but these errors were encountered:
It is common for real-world applications to have several versions of scala-logging in their dependency graphs, which leads to sbt giving eviction warnings.
I couldn't find a documented versioning policy, so I'm not sure when I should be worried. sbt now offers a more formal way than documentation, in the
versionScheme
setting that libraries can declare. It'd be great if scala-logging's build/artifacts include this.Perhaps sbt-version-policy, or MiMa alone, can be employed to keep us honest.
The text was updated successfully, but these errors were encountered: