[jmeter] branch master updated: Fix Gradle commands in readme

[vl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

vladimirsitnikov pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jmeter.git


The following commit(s) were added to refs/heads/master by this push:
     new fae38a3  Fix Gradle commands in readme
fae38a3 is described below

commit fae38a3bee752c9d8cadebf3dfbfb3dd92f92d0c
Author: Vladimir Sitnikov <si...@gmail.com>
AuthorDate: Mon Oct 28 12:35:27 2019 +0300

    Fix Gradle commands in readme
---
 README.md | 25 +++++++++++++++++--------
 1 file changed, 17 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 06dfbe2..c698a86 100644
--- a/README.md
+++ b/README.md
@@ -157,22 +157,31 @@ systemProp.https.proxyPassword=your_password
 
 JMeter is built using Gradle.
 
-Change to the top-level directory and issue the command:
+The following command would build and test JMeter:
 
 ```sh
-./gradlew build
+./gradlew build [-Djava.awt.headless=true]
 ```
 
-This will compile the application and enable you to run `jmeter` from the `bin`
-directory.
+The optional property definition is required if the system
+does not have a suitable GUI display.
+
+The output artifacts (jars, reports) are placed to `build` folders.
+For instance, binary artifacts can be found under `src/dist/build/distributions`.
+
+The following command would compile the application and enable you to run `jmeter` from the `bin`
+directory. Note: it completely refreshes `lib/` contents, so it would remove clustom plugins
+should you have them installed.
 
 ```sh
-./gradlew check [-Djava.awt.headless=true]
+./gradlew createDist
 ```
 
-This will compile and run the unit tests.
-The optional property definition is required if the system
-does not have a suitable GUI display.
+Alternatively you could start GUI via
+
+```sh
+./gradlew runGui
+```
 
 ## Developer information