Karl/BobStore
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix gradlew references in markdown files

Browse Source 
Use gradlew consistently. Also, fix its calling after the cd.
This commit is contained in:
Daniel Martí 2016-03-05 23:33:52 +00:00
parent 80a3faa4d5
commit 26d60aa9ae
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@ -55,7 +55,7 @@ To get all the logcat messages by F-Droid, you can run:
## Building tips ## Building tips
* Use `gradle --daemon` if you are going to build F-Droid multiple times. * Use gradle with `--daemon` if you are going to build F-Droid multiple times.
* If you get a message like `Could not find com.android.support:support-...`, * If you get a message like `Could not find com.android.support:support-...`,
make sure that you have the latest Android support maven repository. make sure that you have the latest Android support maven repository.
@ -65,7 +65,7 @@ In order to run the F-Droid test suite, you will need to have either a real devi
connected via `adb`, or an emulator running. Then, execute the following from the connected via `adb`, or an emulator running. Then, execute the following from the
command line: command line:
gradle connectedCheck ./gradlew connectedCheck
Note that the CI already runs the tests on an emulator, so you don't Note that the CI already runs the tests on an emulator, so you don't
necessarily have to do this yourself if you open a merge request as the tests necessarily have to do this yourself if you open a merge request as the tests

2
README.md
View File

@ -8,7 +8,7 @@ for Android.
## Building with Gradle ## Building with Gradle
cd F-Droid cd F-Droid
./gradlew assembleRelease ../gradlew assembleRelease
## Direct download ## Direct download