Skip to content

Commit 2d0c301

Browse files
committed
Add another way to test changes locally to README.md
1 parent c8abc1a commit 2d0c301

1 file changed

Lines changed: 12 additions & 2 deletions

File tree

README.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,21 @@ NewPipe Extractor is available at JitPack's Maven repo.
1111
If you're using Gradle, you could add NewPipe Extractor as a dependency with the following steps:
1212

1313
1. Add `maven { url 'https://jitpack.io' }` to the `repositories` in your `build.gradle`.
14-
2. Add `compile 'com.github.TeamNewPipe:NewPipeExtractor:v0.11.0'`the `dependencies` in your `build.gradle`. Replace `v0.11.0` with the latest release.
14+
2. Add `implementation 'com.github.TeamNewPipe:NewPipeExtractor:v0.19.0'`the `dependencies` in your `build.gradle`. Replace `v0.19.0` with the latest release.
1515

1616
### Testing changes
1717

18-
To test changes quickly you can build the library locally. Using the local Maven repository is a good approach, here's a gist of how to use it:
18+
To test changes quickly you can build the library locally. A good approach would be to add something like the following to your `settings.gradle`:
19+
20+
```groovy
21+
includeBuild('../NewPipeExtractor') {
22+
dependencySubstitution {
23+
substitute module('com.github.TeamNewPipe:NewPipeExtractor') with project(':extractor')
24+
}
25+
}
26+
```
27+
28+
Another approach would be to use the local Maven repository, here's a gist of how to use it:
1929

2030
1. Add `mavenLocal()` in your project `repositories` list (usually as the first entry to give priority above the others).
2131
2. It's _recommended_ that you change the `version` of this library (e.g. `LOCAL_SNAPSHOT`).

0 commit comments

Comments
 (0)