Deprecate CrossVersion.Disabled (was make CrossVersion.Disabled stable) #316
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
migration note
CrossVersion.Disabled
did not work as expected in sbt 1.0.x ~ 1.2.x.We recommend using
CrossVersion.disabled
instead. For pattern matching, you can either check equality withCrossVersion.disabled
or type match withcase _: sbt.librarymanagement.Disabled
.original PR
Fixes sbt/sbt#4975
Fixes sbt/sbt#4977
This makes
CrossVersion.Disabled
a stable identifier by revertingfinal def
back tofinal val
.This is to fix Scala.JS build
notes
final val Disabled = sbt.librarymanagement.Disabled
but it was just a companion objectfinal val Disabled = sbt.librarymanagement.Disabled()
, but this broke Cat's build that was callingCrossVersion.Disabled()
final def Disabled = sbt.librarymanagement.Disabled
andobject Disabled extends sbt.librarymanagement.Disabled
final val Disabled = sbt.librarymanagement.Disabled
(but because we changed the companion object in make object Disabled extend Disabled #290 that's ok)