Corrected Logging instruction for wrappers READ.me.

Signed-off-by: artem.ivanov <[email protected]>
srottem · Dec 12, 2018 · d0b53ec · d0b53ec
1 parent f6a78a6
commit d0b53ec
Show file tree

Hide file tree

Showing 5 changed files with 16 additions and 7 deletions.
diff --git a/cli/src/main.rs b/cli/src/main.rs
@@ -201,7 +201,7 @@ fn _print_help() {
     println_acc!("\tLoad plugins in Libindy.");
     println_acc!("\tUsage: indy-cli --plugins <lib-1-name>:<init-func-1-name>,...,<lib-n-name>:<init-func-n-name>");
     println!();
-    println_acc!("\tInit logger according to a config file.");
+    println_acc!("\tInit logger according to a config file. \n\tIndy Cli uses `log4rs` logging framework: https://crates.io/crates/log4rs");
     println_acc!("\tUsage: indy-cli --logger-config <path-to-config-file>");
     println!();
 }

diff --git a/vcx/wrappers/java/README.md b/vcx/wrappers/java/README.md
@@ -49,3 +49,6 @@ The jar will be present in `indy-sdk/vcx/wrappers/java/vcx/build/libs`
 - run `./gradlew clean assemble --project-dir=android` in folder `indy-sdk/vcx/wrappers/java/vcx`
 
 Aar will be present in `indy-sdk/vcx/wrappers/java/vcx/android/build/outputs/aar`
+
+#### Logging
+The Java wrapper uses slf4j as a facade for various logging frameworks, such as java.util.logging, logback and log4j.
diff --git a/vcx/wrappers/python3/README.md b/vcx/wrappers/python3/README.md
@@ -22,4 +22,8 @@ python3 generateDocs.py
 * A directory will be created locally `./docs` which contains subdirectories 'vcx' and within that 'api'.  Html files are generated and put here that give details on each api function.
 
 ### Example use
-For the main workflow example check [Python demo](https://github.com/hyperledger/indy-sdk/tree/master/vcx/wrappers/python3/demo).
+For the main workflow example check [Python demo](https://github.com/hyperledger/indy-sdk/tree/master/vcx/wrappers/python3/demo).
+
+#### Logging
+The Python wrapper uses default Python logging module. So, to enable logs you need just to configure its usual way. 
+Note: there is an additional log level=0 that is equal to `trace` level.
diff --git a/wrappers/java/README.md b/wrappers/java/README.md
@@ -38,10 +38,11 @@ Then copy the resulting `libindy.so` to `./lib/`.
 Then run
 
     mvn clean install
-    
-#### Troubleshooting
-Use environment variable `RUST_LOG={info|debug|trace}` to output logs of Libindy.
+
+#### Logging
+The Java wrapper uses slf4j as a facade for various logging frameworks, such as java.util.logging, logback and log4j.
 
+#### Troubleshooting
 If your application that uses libindy crashes with a Null Pointer Exception then probably the libindy shared library could 
 not be loaded properly. If you have build libindy from source then either put the resulting shared library where your
 operating system searches for shared libraries or set appropriate environment variables to help the OS's loader to find them.

diff --git a/wrappers/python/README.md b/wrappers/python/README.md
@@ -40,5 +40,6 @@ Then run
 ### Example use
 For the main workflow examples check tests in demo folder: https://github.com/hyperledger/indy-sdk/tree/master/wrappers/python/tests/demo
 
-#### Troubleshooting
-Use environment variable `RUST_LOG={info|debug|trace}` to output logs of Libindy.
+#### Logging
+The Python wrapper uses default Python logging module. So, to enable logs you need just to configure its usual way. 
+Note: there is an additional log level=0 that is equal to Libindy `trace` level.