Incremental compiler API incompatibility with Scala Compiler 2.13.1

[martin-g]

Upgrading from 2.13.0 to 2.13.1 fails my build with:

[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:4.2.0:compile (scala-compile-first) on project wicketstuff-scala: Execution scala-compile-first of goal net.alchim31.maven:scala-maven-plugin:4.2.0:compile failed: An API incompatibility was encountered while executing net.alchim31.maven:scala-maven-plugin:4.2.0:compile: java.lang.NoSuchMethodError: 'scala.tools.nsc.settings.AbsSettings$AbsSetting scala.tools.nsc.Settings.nowarn()'
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>net.alchim31.maven:scala-maven-plugin:4.2.0
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/martin/.m2/repository/net/alchim31/maven/scala-maven-plugin/4.2.0/scala-maven-plugin-4.2.0.jar
...

Related-to: scala/bug#11742

[slandelle]

Thanks for reporting. Actually, the problem is similar, but here it's a zinc component that gets broken. I've opened an issue against zinc: sbt/zinc#698

Is there any update on this please? Seeing that the discussion over sbt/zinc seems to indicate the "precompiled binary" for compiler-bridge cannot be used.

[slandelle]

Renaming issue to make it clear that only the incremental compiler mode suffers from this incompatibility issue and not the all one.

[slandelle]

@davidB Would you mind cutting a release, please?

[davidB]

@slandelle , I have issue with the release process (I will diseable some of doc generation, api,... - useless). I'll try to release this week.

[slandelle]

Cool, thanks!

[davidB]

4.2.4 published on maven central

[slandelle]

Thanks!