From b98f96fd66f800cf545d36eec94b9ba3739247f0 Mon Sep 17 00:00:00 2001 From: bopol Date: Sun, 19 Apr 2020 16:19:48 +0200 Subject: [PATCH 1/3] Add how to run changes in app: Use local version of NPE --- docs/04_Run_changes_in_App.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/docs/04_Run_changes_in_App.md b/docs/04_Run_changes_in_App.md index 13018e7..973d9fa 100644 --- a/docs/04_Run_changes_in_App.md +++ b/docs/04_Run_changes_in_App.md @@ -22,7 +22,24 @@ sometimes have to adjust the udev rules in order to ### Run Your Changes on the Extractor -In order to use the extractor in our app, we use [JitPack](https://jitpack.io). This is a build service that can build +There are several ways to test your extractor version in NewPipe. We will show you the most convenient ones: + +#### Using local folder + +In NewPipe app root folder, edit [settings.gradle](https://github.com/TeamNewPipe/NewPipe/blob/dev/settings.gradle) file and add this: +``` +includeBuild('../NewPipeExtractor') { + dependencySubstitution { + substitute module('com.github.TeamNewPipe:NewPipeExtractor') with project(':extractor') + } +} +``` +`includeBuild` should be the relative path. `../NewPipeExtractor` means one folder back in hierarchy, +and the folder is name exactly `NewPipeExtractor`. If it's not the case, edit this part. + +#### Using JitPack + +Another way is to use [JitPack](https://jitpack.io). This is a build service that can build maven *.jar packages for Android and Java based on GitHub or GitLab repositories. To use the extractor through JitPack, you need to push it to your online repository of From d8da7c0c1ead0684376c840c52e9328c5fd4150e Mon Sep 17 00:00:00 2001 From: bopol Date: Sun, 19 Apr 2020 20:47:51 +0200 Subject: [PATCH 2/3] correct a sentence --- docs/04_Run_changes_in_App.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/04_Run_changes_in_App.md b/docs/04_Run_changes_in_App.md index 973d9fa..6685ab4 100644 --- a/docs/04_Run_changes_in_App.md +++ b/docs/04_Run_changes_in_App.md @@ -34,8 +34,8 @@ includeBuild('../NewPipeExtractor') { } } ``` -`includeBuild` should be the relative path. `../NewPipeExtractor` means one folder back in hierarchy, -and the folder is name exactly `NewPipeExtractor`. If it's not the case, edit this part. +`includeBuild` should have the relative path as argument. `../NewPipeExtractor` means one folder back in hierarchy, +and the folder is exactly named `NewPipeExtractor`. If that's not the case, edit this part. #### Using JitPack From eaab60a93ab5640e1e9d61a68cf47efab75026e8 Mon Sep 17 00:00:00 2001 From: bopol Date: Sun, 19 Apr 2020 23:30:53 +0200 Subject: [PATCH 3/3] make the sentence clearer: back -> up in hierarchy --- docs/04_Run_changes_in_App.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/04_Run_changes_in_App.md b/docs/04_Run_changes_in_App.md index 6685ab4..1f5937a 100644 --- a/docs/04_Run_changes_in_App.md +++ b/docs/04_Run_changes_in_App.md @@ -34,7 +34,7 @@ includeBuild('../NewPipeExtractor') { } } ``` -`includeBuild` should have the relative path as argument. `../NewPipeExtractor` means one folder back in hierarchy, +`includeBuild` should have the relative path as argument. `../NewPipeExtractor` means one folder up in hierarchy, and the folder is exactly named `NewPipeExtractor`. If that's not the case, edit this part. #### Using JitPack