Mercury-IM/Smack
Mercury-IM/Smack
1
0
Fork 0
mirror of https://codeberg.org/Mercury-IM/Smack synced 2024-11-24 23:32:05 +01:00
Code Issues Releases Wiki Activity

Replace references to 'smack.jar'

Browse source 
Also don't mention the required JDK version in the README as such information
tends to become wrong easily.
This commit is contained in:
Florian Schmaus 2014-07-05 12:04:40 +02:00
parent 08a232bff3
commit 4477561d4b
3 changed files with 6 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
documentation/debugging.html
View file

@ -16,8 +16,8 @@ Debugging with Smack
<p> <p>
Smack includes two built-in debugging consoles that will let you track all XML traffic between Smack includes two built-in debugging consoles that will let you track all XML traffic between
the client and server. A <a href="#lite">lite debugger</a> which is part of the <tt>smack.jar</tt> the client and server. A <a href="#lite">lite debugger</a> which is part of the <tt>smack-core.jar</tt>
and an <a href="#enhanced">enhanced debugger</a> contained in <tt>smackx-debug.jar</tt>. and an <a href="#enhanced">enhanced debugger</a> contained in <tt>smack-debug.jar</tt>.
</p> </p>
<p> <p>
@ -56,7 +56,7 @@ Smack uses the following logic to decide the debugger console to use:
<li>If step 1 fails then Smack will try to use the enhanced debugger. The <li>If step 1 fails then Smack will try to use the enhanced debugger. The
file <tt>smackx-debug.jar</tt> contains the enhanced debugger. Therefore you will need file <tt>smackx-debug.jar</tt> contains the enhanced debugger. Therefore you will need
to place the jar file in the classpath. For situations where space is an issue you to place the jar file in the classpath. For situations where space is an issue you
may want to only deploy <tt>smack.jar</tt> in which case the enhanced debugger won't be may want to only deploy <tt>smack-core.jar</tt> in which case the enhanced debugger won't be
available.<p> available.<p>
<li>The last option if the previous two steps fail is to use the lite debugger. The lite <li>The last option if the previous two steps fail is to use the lite debugger. The lite

4
resources/README.html
View file

@ -55,9 +55,9 @@ possible, instructions are provided for both Unix/Linux and Windows users.
<p> <p>
<b><a name="javaSetup">Configure Java</a></b> <b><a name="javaSetup">Configure Java</a></b>
<ul> <ul>
Java 6 (JDK 1.6 or later) must be installed and setup on your machine. To test the installation, A Java Development Kit (JDK) must be installed and setup on your machine. To test the installation,
open a shell in a Unix or a MS-DOS prompt in Windows. Check your version of open a shell in a Unix or a MS-DOS prompt in Windows. Check your version of
Java with "java -version". Java with "javac -version".
If Java isn't installed, download a copy from the If Java isn't installed, download a copy from the
<a href="http://java.oracle.com/">Java website</a>. <a href="http://java.oracle.com/">Java website</a>.
</ul> </ul>

3
smack-core/src/main/java/org/jivesoftware/smack/SmackConfiguration.java
View file

@ -52,8 +52,7 @@ import org.xmlpull.v1.XmlPullParserException;
* via the API will override settings in the configuration file. * via the API will override settings in the configuration file.
* </ul> * </ul>
* *
* Configuration settings are stored in org.jivesoftware.smack/smack-config.xml (typically inside the * Configuration settings are stored in org.jivesoftware.smack/smack-config.xml.
* smack.jar file).
* *
* @author Gaston Dombiak * @author Gaston Dombiak
*/ */