Scala 2.12 artifacts

[eed3si9n]

Could we cross build to Scala 2.12 please? sbt 1 plugins would need it.

[szeiger]

Hm, I don't even remember how I published this the last time. Looks completely manual as far as I can tell from the repo. Note that we already cross-build and test for 2.11 and 2.12 so we'd only have to publish the additional artifacts for mima-core.

Is there already a way to build sbt plugins with 2.12 for sbt 1.0? Then we could also publish mima-reporter.

[SethTisue]

release steps (sadly numerous) can be copy/pasted from #165 (more detailed than https://github.com/typesafehub/migration-manager/wiki/Releasing-MiMa)

the needed changes for 2.12 are on this branch: https://github.com/typesafehub/migration-manager/tree/scala-2.12 which is included in the 2.12 community build. other than the community build runs, probably nobody has looked at the branch in a while now ("51 commits behind master")

in order to publish everything from one branch, I guess we'd need separate scala-2.10 and scala-2.12 source directories?

[szeiger]

Oh, you're right, we're only setting testScalaVersion to 2.11 and 2.12 but we haven't built it on 2.12 yet.

[szeiger]

Abstracting this out into scala-2.10 and scala-2.12 turns out to be rather tricky due to the pervasive differences in classpath handling. I have a version that compiles but it's still buggy.

[2m]

Core and reporter is Scala 2.12 ready. Sbt Plugin is the only one left.

[irundaia]

@2m would it be possible to publish the core and reporter artefacts for scala 2.11/2.12? This would make incorporating mima in other build tools easier

[SethTisue]

I see over at #179 #180 this is getting close.

UPDATE: actually #180 was merged, so now it just remains to do a release

[SethTisue]

there are mutterings coming from @dwijnand's direction about doing a release

[dwijnand]

https://github.com/typesafehub/migration-manager/releases/tag/0.1.15