Skip to content

Conversation

lrytz
Copy link
Member

@lrytz lrytz commented Apr 29, 2015

Review by @adriaanm

lrytz added 2 commits April 29, 2015 16:40
Modules have to specify the `mimaPreviousVersion` property. MiMa is NOT executed if - the above property is not set - but the module of version mimaPreviousVersion cannot be resolved against the scalaBinaryVersion A warning is issued if MiMa is skipped.
It only has an effect if the Scala version number is exactly 2.11.0-SNAPSHOT. For 2.11.x-SNAPSHOT with x > 0, sbt already sets the scalaBinaryVersion to 2.11. Note that our nightly release builds don't use -SNAPSHOT for the Scala version, but something like 2.12.0-[sha]-nightly.
@adriaanm
Copy link
Contributor

LGTM! Very nice.

@lrytz
Copy link
Member Author

lrytz commented Apr 29, 2015

cool! i'll tag this as v1.0.3.

lrytz added a commit that referenced this pull request Apr 29, 2015
Add MiMa, remove snapshotScalaBinaryVersion
@lrytz lrytz merged commit 894fc14 into scala:master Apr 29, 2015
@lrytz lrytz deleted the mima branch April 30, 2015 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants