Downgrade scala-parser-combinators to 1.x because of version conflicts

[mkurz]

Reproducer:

sbt new playframework/play-scala-seed.g8
cd play-scala-seed/
# Edit project/plugins.sbt, change sbt-giter8-scaffold version to 0.15.0
# Now run sbt:
sbt

You end up with:

[error]         * org.scala-lang.modules:scala-parser-combinators_2.12:2.1.1 (early-semver) is selected over {1.1.2, 1.1.1}
[error]             +- org.foundweekends.giter8:giter8-lib_2.12:0.15.0    (depends on 2.1.1)
[error]             +- com.typesafe.sbt:sbt-native-packager:1.5.2 (scalaVersion=2.12, sbtVersion=1.0) (depends on 1.1.1)
[error]             +- com.typesafe.play:sbt-routes-compiler_2.12:2.8.16  (depends on 1.1.2)

The problem is that most sbt plugins didn't upgrade to scala-parser-combinators v2 yet, so that's why this version conflicts occur.
Even the latest release of Scala 2.12 stays on v1 for now: https://github.com/scala/scala/blob/v2.12.17/versions.properties#L22
(But they did upgrade to scala-xml 2.x in 2.12.17 release however)

That's why I think it makes sense to downgrade in giter8 for now, until there is like a consens in the Scala world when plugins (that run on Scala 2.12) upgrade to v2. (That happened with scala-xml recently, where the scala-compiler and many sbt plugins upgraded scala-xml to v2)

Would it be possible to release 0.15.1 or 0.16 with that pr merged? Thanks!

[eed3si9n]

Thanks! This makes sense to me.

[mkurz]

PR is green, @eed3si9n would you mind cutting a new release? Thanks!

[mkurz]

Sorry for nagging 👀 Has someone time to release a new version? Thank you!

[eed3si9n]

I released two versions

• https://github.com/foundweekends/giter8/releases/tag/v0.15.1 (Backports this PR on top of 0.15.0)
• https://github.com/foundweekends/giter8/releases/tag/v0.16.0 (this PR + Scala version bumps)

[mkurz]

Thanks!