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
{{ message }}
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
The plugin should check if libraries in the catalog are binary compatible, in order to prevent issues when using its default values.
At this moment, the plugin skips this lack of checking providing a custom DSL to use the library versions that fit better on the project using sbt-org-policies. For example:
%%("http4s") => by default will use the last one: "0.18.0-M1"
But you could use it in this way, to force the use of a different version of the artifact:
The plugin should check if libraries in the catalog are binary compatible, in order to prevent issues when using its default values.
At this moment, the plugin skips this lack of checking providing a custom DSL to use the library versions that fit better on the project using
sbt-org-policies
. For example:%%("http4s")
=> by default will use the last one:"0.18.0-M1"
But you could use it in this way, to force the use of a different version of the artifact:
%%("http4s", "0.17.0-M3")
We could make this enforcement as a part of the existing autocheck task: https://github.com/47deg/sbt-org-policies/blob/4c615587575f654a9fce3f58dd25a55987b80c44/autocheck/build.sbt#L34
The text was updated successfully, but these errors were encountered: