sam-byng opened a new pull request, #11:
URL: https://github.com/apache/incubator-pekko-samples/pull/11

   incubator-pekko issue : https://github.com/apache/incubator-pekko/issues/243
   
   
   **Method:**
   Steps taken from updated migration guide in PR:
   In your `pom.xml` and `build.sbt` files:
   * Update dependency Akka version to the latest Pekko version.
   * for Pekko jar dependencies, the groupId is `org.apache.pekko` instead of 
`com.typesafe.akka` or `com.lightbend.akka.<package_name>`
   * the jar names (i.e. the `artifactId` field in `pom.xml`) start with 
"pekko" instead of "akka" - e.g. pekko-actor_2.13.jar instead of 
akka-actor_2.13.jar
   * Alpakka equivalent is "pekko-connectors" - e.g. 
pekko-connectors-kafka_2.13.jar instead of alpakka-kafka_2.13.jar
   
   In source code files:
   * Pekko packages start with `org.apache.pekko` instead of `akka` - e.g. 
`import org.apache.pekko.actor` instead of `import akka.actor`
   * Where class names have "Akka" in the name, the Pekko ones have "Pekko" - 
e.g. `PekkoException` instead of `AkkaException`
   * Config changes use `pekko` prefix instead of `akka`
   
   In config files for your module:
   * Configs use `pekko` prefix instead of `akka`
   
   In Documentation:
   * Where appropriate, text should refer to `Pekko` instead of `Akka`
   * URLs linking to files in https://doc.akka.io/docs/akka/ should instead 
point at https://pekko.apache.org/docs/pekko/
   
   *Note: I checked the lightbend.akka.grpc project and those packages are 
going to org.apache.pekko so assuming this is the case for all


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to