From e0dcc7766b1063ab5373db31ac7670b977352efa Mon Sep 17 00:00:00 2001
From: Arnout Engelen <github@bzzt.net>
Date: Thu, 9 Nov 2017 09:16:30 +0100
Subject: [PATCH] sbt1 camelcases commands (#23932)

---
 akka-docs/src/main/paradox/multi-jvm-testing.md  | 12 ++++++------
 akka-docs/src/main/paradox/multi-node-testing.md | 10 +++++-----
 2 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/akka-docs/src/main/paradox/multi-jvm-testing.md b/akka-docs/src/main/paradox/multi-jvm-testing.md
index 6a9e8ad9c4..b44151416d 100644
--- a/akka-docs/src/main/paradox/multi-jvm-testing.md
+++ b/akka-docs/src/main/paradox/multi-jvm-testing.md
@@ -25,7 +25,7 @@ Here is an example of a @extref[sample project](samples:akka-sample-multi-node-s
 
 ## Running tests
 
-The multi-JVM tasks are similar to the normal tasks: `test`, `test-only`,
+The multi-JVM tasks are similar to the normal tasks: `test`, `testOnly`,
 and `run`, but are under the `multi-jvm` configuration.
 
 So in Akka, to run all the multi-JVM tests in the akka-remote project use (at
@@ -43,20 +43,20 @@ project akka-remote-tests
 multi-jvm:test
 ```
 
-To run individual tests use `test-only`:
+To run individual tests use `testOnly`:
 
 ```none
-multi-jvm:test-only akka.remote.RandomRoutedRemoteActor
+multi-jvm:testOnly akka.remote.RandomRoutedRemoteActor
 ```
 
 More than one test name can be listed to run multiple specific
 tests. Tab-completion in sbt makes it easy to complete the test names.
 
-It's also possible to specify JVM options with `test-only` by including those
+It's also possible to specify JVM options with `testOnly` by including those
 options after the test names and `--`. For example:
 
 ```none
-multi-jvm:test-only akka.remote.RandomRoutedRemoteActor -- -Dsome.option=something
+multi-jvm:testOnly akka.remote.RandomRoutedRemoteActor -- -Dsome.option=something
 ```
 
 ## Creating application tests
@@ -190,7 +190,7 @@ class SpecMultiJvmNode2 extends WordSpec with MustMatchers {
 }
 ```
 
-To run just these tests you would call `multi-jvm:test-only sample.Spec` at
+To run just these tests you would call `multi-jvm:testOnly sample.Spec` at
 the sbt prompt.
 
 ## Multi Node Additions
diff --git a/akka-docs/src/main/paradox/multi-node-testing.md b/akka-docs/src/main/paradox/multi-node-testing.md
index 69aff363d6..a457b14e55 100644
--- a/akka-docs/src/main/paradox/multi-node-testing.md
+++ b/akka-docs/src/main/paradox/multi-node-testing.md
@@ -121,10 +121,10 @@ Here are some examples of how you define hosts:
 ### Running the Multi Node Tests
 
 To run all the multi node test in multi-node mode (i.e. distributing the jar files and kicking off the tests
-remotely) from inside sbt, use the `multi-node-test` task:
+remotely) from inside sbt, use the `multiNodeTest` task:
 
 ```none
-multi-node-test
+multiNodeTest
 ```
 
 To run all of them in multi-jvm mode (i.e. all JVMs on the local machine) do:
@@ -133,16 +133,16 @@ To run all of them in multi-jvm mode (i.e. all JVMs on the local machine) do:
 multi-jvm:test
 ```
 
-To run individual tests use the `multi-node-test-only` task:
+To run individual tests use the `multiNodeTestOnly` task:
 
 ```none
-multi-node-test-only your.MultiNodeTest
+multiNodeTestOnly your.MultiNodeTest
 ```
 
 To run individual tests in the multi-jvm mode do:
 
 ```none
-multi-jvm:test-only your.MultiNodeTest
+multi-jvm:testOnly your.MultiNodeTest
 ```
 
 More than one test name can be listed to run multiple specific tests. Tab completion in sbt makes it easy to