Upgrade scala-module-plugin, use scalaVersionsByJvm #111

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

Jump to bottom

Closed

gourlaysama wants to merge 2 commits into scala:1.0.x from gourlaysama:new-scala-sbt-module

Closed

Upgrade scala-module-plugin, use scalaVersionsByJvm #111

gourlaysama wants to merge 2 commits into scala:1.0.x from gourlaysama:new-scala-sbt-module

Conversation

gourlaysama

Copy link

Contributor

@gourlaysama gourlaysama commented Apr 24, 2017

Upgrade to:
- scala 2.11.11, 2.12.2
- latest scala-module-plugin, with scalaVersionByJvm
- latest sbt
- latest scala-js
Add support for republishing an old version against a new Scala version (from Upgrade scala-module-plugin, use scalaVersionsByJvm scala-swing#60 )

I'll add support for 2.13.0-M1 as soon as the scala-js plugin becomes available.

gourlaysama added 2 commits

April 24, 2017 20:35

@gourlaysama


 move to latest scala, sbt & plugins versions

02da785

 - scala 2.11.11, 2.12.2 (no 2.13.0-M1 yet)
 - latest `scala-sbt-module`, with `scalaVersionByJvm`
 - latest sbt
 - latest scala-js

@gourlaysama


 add support for publishing an old release against a new Scala

200e424

taken from scala/scala-swing#60

@gourlaysama gourlaysama requested a review from lrytz

April 24, 2017 20:07

@lrytz

Copy link

Member

lrytz commented Apr 25, 2017

Hey, I have a re-work of 1.0.6 going on, will publish that today. The scalaVersionsByJvm doesn't work well for multi-project builds if scalaModuleSettings is only enabled in one projects (scala-parallel-collections).