From dcd0fd87b35bd6c78719246f95f5e491ebb4142c Mon Sep 17 00:00:00 2001 From: Simon Schuster Date: Mon, 10 Sep 2018 11:49:51 +0200 Subject: [PATCH] Documentation: debugging: The debugging jar is now named smack-debug.jar The documentation states that the debugging jar is called smackx-debug.jar. However, according to maven central, that name was only used until 3.2.1, newer releases (including 4.4.0-alpha1) only distribute smack-debug.jar, which contains the debugger as advertised. --- documentation/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/debugging.md b/documentation/debugging.md index 41f236172..f718f865f 100644 --- a/documentation/debugging.md +++ b/documentation/debugging.md @@ -29,7 +29,7 @@ Smack uses the following logic to decide the debugger console to use: `java -Dsmack.debuggerClass=my.company.com.MyDebugger SomeApp ` - 2. If step 1 fails then Smack will try to use the enhanced debugger. The file `smackx-debug.jar` contains the enhanced debugger. Therefore you will need to place the jar file in the classpath. For situations where space is an issue you may want to only deploy `smack-core.jar` in which case the enhanced and lite debugger won't be available, but only the console debugger. + 2. If step 1 fails then Smack will try to use the enhanced debugger. The file `smack-debug.jar` contains the enhanced debugger. Therefore you will need to place the jar file in the classpath. For situations where space is an issue you may want to only deploy `smack-core.jar` in which case the enhanced and lite debugger won't be available, but only the console debugger. 3. The last option if the previous two steps fail is to use the console debugger. The console debugger is a very good option for situations where you need to have low memory footprint.