* modified all references in docs module
* replaced in inline scala docs
* renamed variable and changed access specifier
* reanmed in remaining places
* Adjusted path (instead of `akka` used `pekko`)
* Where applicable akka.io is replaced with pekko.apache.org
* replaced akka with pekko in the path
* Removed TODO
* Removed migration guide to gRPC (there is no user using pekko at the moment so no need of migration guide)
* Added back migration to gRPC section
* removed TODO
* alpakka is replaced with pekko-connectors
* the Akka online documentation -> the Pekko online documentation
* referring akka security docs
* reffering to akka migration guides (pekko is not managing them)
* Using pekkoBaseURL for platform-guide.base_url
* removed unnecessary redirects and used current instead of 2.6
* Changed akka discovery to pekko discovery
* Some more replacement
* fix merge issue
* revert platform-guide change because we
---------
Co-authored-by: PJ Fanning <pjfanning@users.noreply.github.com>
* Move more release instructions to the template
Sparked by discussion in #17432
* use newer version in example
Co-authored-by: Renato Cavalcanti <renato@cavalcanti.be>
* point to sonatype for snapshots
Co-authored-by: Renato Cavalcanti <renato@cavalcanti.be>
Since the updated github issues views, it shows all "removed tags",
events in the issue even if the removed tag was never set on the issue.
So this script would always show up as "removed validating,needs-attention"
Even if the issue never had the label needs-attention set to it,
which is confusing visually.
This change introduces that we only remove tags that actually are set on
the issue.
* The Java with Lambda support documentation for AbstractActor and AbstractFSM are now on par with Scala
* Many small fixes and additions of missing things
* Added an AbstractActorContext that has convenience functions for getChild and getChildren
- restructure message classes in sealed traits according to message flow
direction and include confirmed/unconfirmed status in the type
- add GetAddress query for obtaining the remote transport address of
another test participant
- add reconnects to Player
- add small DSL with runOn(node...), ifNode(node...)(<true>)(<false>)
and node(<node>):ActorPath
- rewrite TestConductorSpec to use that DSL and run within a single test
procedure instead of separate NodeX classes
- hook up that test into current multi-jvm infrastructure temporarily
for testing (will use Björn’s new remote-multi-jvm stuff later)
