direct usage of library project

Signed-off-by: tobiasKaminsky <tobias@kaminsky.me>
This commit is contained in:
tobiasKaminsky 2019-04-17 07:17:24 +02:00
parent 4062d40aa6
commit 52020a9bf3
No known key found for this signature in database
GPG key ID: 0E00D4D47D0C5AF7

View file

@ -85,3 +85,23 @@ The app is currently equipped to be built with three flavours:
[6]: https://developer.android.com/sdk/installing/index.html?pkg=studio [6]: https://developer.android.com/sdk/installing/index.html?pkg=studio
[7]: https://gradle.org/ [7]: https://gradle.org/
[8]: https://docs.gradle.org/current/userguide/gradle_wrapper.html [8]: https://docs.gradle.org/current/userguide/gradle_wrapper.html
### 5. How-To
#### 1. Direct usage of library project
This is handy if one wants to make changes both to files app and library:
- in files app root: ln -s $pathToLibraryProject nextcloud-android-library
- uncomment in build.gradle:
- `// implementation project('nextcloud-android-library')`
- comment in build.gradle:
- `genericImplementation 'com.github.nextcloud:android-library:master-SNAPSHOT'`
- `gplayImplementation 'com.github.nextcloud:android-library:master-SNAPSHOT'`
- `versionDevImplementation 'com.github.nextcloud:android-library:master-SNAPSHOT'`
- comment in settings.gradle:
- `include ':'`
- uncomment in settings.gradle:
- `//include 'nextcloud-android-library'`
- sync project with gradle files
Now every change in library can be directly used in files app.