From a84a18d26255718b49e5c47d02090fda2110cf94 Mon Sep 17 00:00:00 2001 From: Johannes Rudolph Date: Tue, 18 Sep 2018 12:48:03 +0200 Subject: [PATCH] Docs: don't use $code$ for now in doc snippets --- akka-docs/src/main/paradox/cluster-usage.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/akka-docs/src/main/paradox/cluster-usage.md b/akka-docs/src/main/paradox/cluster-usage.md index ecf0917879..867b7071ec 100644 --- a/akka-docs/src/main/paradox/cluster-usage.md +++ b/akka-docs/src/main/paradox/cluster-usage.md @@ -429,19 +429,19 @@ This is expected behavior. When the node has been accepted in the cluster you wi receive `MemberUp` for that node, and other nodes. Scala -: @@snip [SimpleClusterListener2.scala]($code$/scala/docs/cluster/SimpleClusterListener2.scala) { #join #subscribe } +: @@snip [SimpleClusterListener2.scala](/akka-docs/src/test/scala/docs/cluster/SimpleClusterListener2.scala) { #join #subscribe } Java -: @@snip [SimpleClusterListener2.java]($code$/java/jdocs/cluster/SimpleClusterListener2.java) { #join #subscribe } +: @@snip [SimpleClusterListener2.java](/akka-docs/src/test/java/jdocs/cluster/SimpleClusterListener2.java) { #join #subscribe } To avoid receiving an empty `CurrentClusterState` at the beginning, you can use it like shown in the following example, to defer subscription until the `MemberUp` event for the own node is received: Scala -: @@snip [SimpleClusterListener2.scala]($code$/scala/docs/cluster/SimpleClusterListener2.scala) { #join #register-on-memberup } +: @@snip [SimpleClusterListener2.scala](/akka-docs/src/test/scala/docs/cluster/SimpleClusterListener2.scala) { #join #register-on-memberup } Java -: @@snip [SimpleClusterListener2.java]($code$/java/jdocs/cluster/SimpleClusterListener2.java) { #join #register-on-memberup } +: @@snip [SimpleClusterListener2.java](/akka-docs/src/test/java/jdocs/cluster/SimpleClusterListener2.java) { #join #register-on-memberup } If you find it inconvenient to handle the `CurrentClusterState` you can use