Migration Guides
- If you are currently using an old version of Akka HTTP or Spray, you should first follow the Akka HTTP migration guide
- The migration guide for the core Apache Pekko libs is a useful guideline.
- for Pekko jar dependencies, the groupId is “org.apache.pekko” instead of “com.typesafe.akka”
- the jar names start with “pekko” instead of “akka” - e.g. pekko-http_2.13.jar instead of akka-http_2.13.jar
- If you have a dependency akka-http2-support, Pekko does not need a separate jar. The support is built into main pekko-http jars.
- Pekko packages start with “org.apache.pekko” instead of “akka” - e.g.
import org.apache.pekko.http
instead ofimport akka.http
- Where class names have “Akka” in the name, the Pekko ones have “Pekko” - e.g. PekkoException instead of AkkaException
- Configs in
application.conf
use “pekko” prefix instead of “akka” - We will soon provide a more detailed guide for migrating from Akka HTTP v10.2 to Apache Pekko HTTP
- If you happen to be using akka-http-cors this has been directly integrated into Apache Pekko Http which means you should use the pekko-http-cors artifact instead. Note that the root configuration naming has also been updated (i.e. changing from
akka-http-cors
topekko.http.cors
) to make it consistent with the rest of Apache Pekko Http. - In addition there is a single breaking change, the return type of the
org.apache.pekko.http.cors.javadsl.settings.CorsSettings.getMaxAge
method has been changed fromjava.util.Optional<Long>
tojava.util.OptionalLong
since it’s more idiomatic.
1.1.0