* Remove use of getClass in secondary constructors
As this is not allowed anymore on newer versions of scala, and likely
didn't work correctly in the past either
This might make selecting unique actor system names for test
actor systems a bit less reliable, but that didn't seem to be
critical anyway.
Thanks to @som-snytt for the heads-up and initial implementation
in #28353
* Avoid AkkaSpec.getCallerName in MultiNodeClusterShardingConfig
* StreamSpec can be abstract
* Use more sophisticated test class name logic
* scalafmt
* Untyped to classic naming convention #24717
* Added entry of naming convention change to migration docs.
* Rename `toUntyped` to `toClassic` in adapters
* Java API compile coverage of the classic testkit
* API coverage of the typed Java testkit (looks good)
* New name for allOf with duration to allow usage from Java #27492
* previous `schedule` method is trying to maintain a fixed average frequency
over time, but that can result in undesired bursts of scheduled tasks after a long
GC or if the JVM process has been suspended, same with all other periodic
scheduled message sending via various Timer APIs
* most of the time "fixed delay" is more desirable
* we can't just change because it's too big behavioral change and some might
depend on previous behavior
* deprecate the old `schedule` and introduce new `scheduleWithFixedDelay`
and `scheduleAtFixedRate`, when fixing the deprecation warning users should
make a concious decision of which behavior to use (scheduleWithFixedDelay in
most cases)
* Streams
* SchedulerSpec
* test both fixed delay and fixed rate
* TimerSpec
* FSM and PersistentFSM
* mima
* runnable as second parameter list, also in typed.Scheduler
* IllegalStateException vs SchedulerException
* deprecated annotations
* api and reference docs, all places
* migration guide
* Fix remaining akka-testkit warnings
Mostly in tests and 2.13
* Add issue link
* MiMa exclude for multi-node-testkit
We don't promise bincompat there anyway, but perhaps good to keep mima there
so at least we don't break things accidentally
* ⇒, →, ←
* because we don't want to show them in documentation snippets and
then it's complicated to avoid that when snippets are
located in src/test/scala in individual modules
* dont replace object `→` in FSM.scala and PersistentFSM.scala
* Harden RemoteConnectionSpec
* Select a free port on the same interface for the second actor system
rather than the random one
* Use config to determine tcp/udp for free port in Artery tests
* Add CopyrightHeader support for sbt-boilerplate plugin.
* Add CopyrightHeader support for `*.proto` files.
* Add regex match for both `–` and `-` for CopyrightHeader.
* Add CopyrightHeader support for sbt build files.
* Update copyright from 2018 to 2019.
* Basic working java api
* Most of the compile only spec in java
* Bits and bobs
* Abstract class for java dsl
* Move to using an abstract class for java dsl
* Wip, playing with not needed classes
* Docs ported to java and removal of the class objects
* java docs for recovery and tagging
* =tkt port WithLogCapturing from akka-http
* =str use WithLogCapturing for very noisy TLSSpec
* =sha use WithLogCapturing to silence noisy CoordinatedShutdownShardingSpec
* re-implement javadsl testkit
* fix mima problem
* rebase master
* move ImplicitSender/DefaultTimeout to scaladsl
* undo the change of moving scala api
* fix return type and add doc
* resolve conflicts and add more comments
* speedup ActorCreationPerfSpec
* reduce iterations in ConsistencySpec
* tag SupervisorHierarchySpec as LongRunningTest
* various small speedups and tagging in actor-tests
* speedup expectNoMsg in stream-tests
* tag FramingSpec, and reduce iterations
* speedup QueueSourceSpec
* tag some stream-tests
* reduce iterations in persistence.PerformanceSpec
* reduce iterations in some cluster perf tests
* tag RemoteWatcherSpec
* tag InterpreterStressSpec
* remove LongRunning from ClusterConsistentHashingRouterSpec
* sys property to disable multi-jvm tests in test
* actually disable multi-node tests in validatePullRequest
* doc sbt flags in CONTRIBUTING
This is useful in at least two scenarios:
- Unit testing actors that communicate to their parent directly
- Testing re-creating (typically persistent) actors with the same name
