Since sbt-dynver now takes care of this and has successfully been tested with
the play and lagom nightly builds. If you really want to override the version
anyway, you can still add a 'version.sbt' and override 'version in ThisBuild'
and 'isSnapshot in ThisBuild' manually.
Extend JUnitSuite to make sure the test is included in the report.
After merging this, nothing would happen. We should then invoke
`checkTestsHaveRun` from the jenkins nightly builds. That should then
fail the build until we merge #28347 and switch the nightly builds
to run on JDK11.
* Unfortunately it seems the jdk9-only tests could not actually be compiled.
With these changes those can actually be compiled and ran again.
* Always link to jdk11 for java.* javadocs
* Update sbt-paradox-akka to fix linking to inner classes for javadoc
* Scala 2.13.0 -> Scala 2.13.1
* Update to genjavadoc 0.15
* Allow 'higherKinds' without explicit import
To follow the 2.13.1 convention
* Remaining higherKinds imports
* Mima excludes for missing value classes in generics
For details on how these differ see:
https://www.scala-sbt.org/1.x/docs/Cross-Build.html#More+about+using+cross-built+libraries
The motivaton for this is so this part of the build doesn't need to be
(ironically) patched when running with a binary-compatible build of the
next patch release of Scala (e.g. Scala 2.13.2-bin-SHA).
Ideally this could be backported to the release-2.5 branch so it would
be immediately of use, otherwise it'll only be available in the
community builds that track Akka 2.6.
This should have been implicit with the -release flag, and now
this indeed appears to be the case. Tested with 2.12 and 2.13.0
Fixes the scalac part of #27079
Only akka-actor got the protobuf files due to the assembled jar being
added to the unmanaged jars for ease of use when importing into
Intellij. Removing that from default settings seems to have fixed it.
Fixes
* Remove protobuf Any import from doc spec
