diff --git a/akka-docs/rst/cluster/cluster-usage-java.rst b/akka-docs/rst/cluster/cluster-usage-java.rst index a6c1542529..09a4f6d3c8 100644 --- a/akka-docs/rst/cluster/cluster-usage-java.rst +++ b/akka-docs/rst/cluster/cluster-usage-java.rst @@ -54,22 +54,7 @@ ip-addresses or host names of the machines in ``application.conf`` instead of `` .. literalinclude:: ../../../akka-samples/akka-sample-cluster/src/main/java/sample/cluster/simple/japi/SimpleClusterApp.java :language: java -3. Add `maven exec plugin `_ to your pom.xml:: - - - - - - org.codehaus.mojo - exec-maven-plugin - 1.2.1 - - - - - - -4. Start the first seed node. Open a terminal window and run (one line):: +3. Start the first seed node. Open a terminal window and run (one line):: mvn exec:java -Dexec.mainClass="sample.cluster.simple.japi.SimpleClusterApp" \ -Dexec.args="2551" @@ -77,7 +62,7 @@ ip-addresses or host names of the machines in ``application.conf`` instead of `` 2551 corresponds to the port of the first seed-nodes element in the configuration. In the log output you see that the cluster node has been started and changed status to 'Up'. -5. Start the second seed node. Open another terminal window and run:: +4. Start the second seed node. Open another terminal window and run:: mvn exec:java -Dexec.mainClass="sample.cluster.simple.japi.SimpleClusterApp" \ -Dexec.args="2552" @@ -89,7 +74,7 @@ and becomes a member of the cluster. Its status changed to 'Up'. Switch over to the first terminal window and see in the log output that the member joined. -6. Start another node. Open a maven session in yet another terminal window and run:: +5. Start another node. Open a maven session in yet another terminal window and run:: mvn exec:java -Dexec.mainClass="sample.cluster.simple.japi.SimpleClusterApp"