Fix Gradle commands in readme

This commit is contained in:
Vladimir Sitnikov 2019-10-28 12:35:27 +03:00
parent b6205c44f8
commit fae38a3bee
1 changed files with 19 additions and 10 deletions

View File

@ -157,23 +157,32 @@ systemProp.https.proxyPassword=your_password
JMeter is built using Gradle. JMeter is built using Gradle.
Change to the top-level directory and issue the command: The following command would build and test JMeter:
```sh ```sh
./gradlew build ./gradlew build [-Djava.awt.headless=true]
``` ```
This will compile the application and enable you to run `jmeter` from the `bin`
directory.
```sh
./gradlew check [-Djava.awt.headless=true]
```
This will compile and run the unit tests.
The optional property definition is required if the system The optional property definition is required if the system
does not have a suitable GUI display. 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 createDist
```
Alternatively you could start GUI via
```sh
./gradlew runGui
```
## Developer information ## Developer information
Building and contributing is explained in details at [building JMeter](https://jmeter.apache.org/building.html) Building and contributing is explained in details at [building JMeter](https://jmeter.apache.org/building.html)