You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by ma...@apache.org on 2014/10/05 04:37:09 UTC
[5/6] git commit: Use Log4jReleaseVersion variable and fix $dollar
stuff.
Use Log4jReleaseVersion variable and fix $dollar stuff.
Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/cf97c0f0
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/cf97c0f0
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/cf97c0f0
Branch: refs/heads/master
Commit: cf97c0f07ca03b80a9673c09b6914bf089d429da
Parents: 01f97a3
Author: Matt Sicker <ma...@apache.org>
Authored: Sat Oct 4 21:04:24 2014 -0500
Committer: Matt Sicker <ma...@apache.org>
Committed: Sat Oct 4 21:04:24 2014 -0500
----------------------------------------------------------------------
src/site/xdoc/manual/jmx.xml.vm | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/cf97c0f0/src/site/xdoc/manual/jmx.xml.vm
----------------------------------------------------------------------
diff --git a/src/site/xdoc/manual/jmx.xml.vm b/src/site/xdoc/manual/jmx.xml.vm
index b4d9428..3a6498c 100644
--- a/src/site/xdoc/manual/jmx.xml.vm
+++ b/src/site/xdoc/manual/jmx.xml.vm
@@ -15,7 +15,7 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
+#set($dollar = '$')
<document xmlns="http://maven.apache.org/XDOC/2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd">
@@ -52,7 +52,7 @@
<p>To perform local monitoring you don't need to specify any system
properties. The JConsole tool that is included in the Java JDK can be
used to monitor your application. Start JConsole by typing
- <code>$JAVA_HOME/bin/jconsole</code> in a command shell.
+ <code>${dollar}JAVA_HOME/bin/jconsole</code> in a command shell.
For more details, see Oracle's documentation on
<a href="http://docs.oracle.com/javase/7/docs/technotes/guides/management/jconsole.html">how to use JConsole</a>.</p>
</subsection>
@@ -89,9 +89,9 @@
<p>To run the Log4j JMX Client GUI as a JConsole Plug-in,
start JConsole with the following command:
</p>
- <p><code>$JAVA_HOME/bin/jconsole -pluginpath /path/to/log4j-api-${project.version}.jar:/path/to/log4j-core-${project.version}.jar:/path/to/log4j-jmx-gui-${project.version}.jar</code></p>
+ <p><code>${dollar}JAVA_HOME/bin/jconsole -pluginpath /path/to/log4j-api-${Log4jReleaseVersion}.jar:/path/to/log4j-core-${Log4jReleaseVersion}.jar:/path/to/log4j-jmx-gui-${Log4jReleaseVersion}.jar</code></p>
<p>or on Windows:</p>
- <p><code>%JAVA_HOME%\bin\jconsole -pluginpath \path\to\log4j-api-${project.version}.jar;\path\to\log4j-core-${project.version}.jar;\path\to\log4j-jmx-gui-${project.version}.jar</code></p>
+ <p><code>%JAVA_HOME%\bin\jconsole -pluginpath \path\to\log4j-api-${Log4jReleaseVersion}.jar;\path\to\log4j-core-${Log4jReleaseVersion}.jar;\path\to\log4j-jmx-gui-${Log4jReleaseVersion}.jar</code></p>
<p>If you execute the above command and connect to your application,
you will see an extra "Log4j 2" tab in the JConsole window.
This tab contains the client GUI, with the StatusLogger selected.
@@ -132,9 +132,9 @@
<p>To run the Log4j JMX Client GUI as a stand-alone application,
run the following command:
</p>
- <p><code>$JAVA_HOME/bin/java -cp /path/to/log4j-api-${project.version}.jar:/path/to/log4j-core-${project.version}.jar:/path/to/log4j-jmx-gui-${project.version}.jar org.apache.logging.log4j.jmx.gui.ClientGui <options></code></p>
+ <p><code>${dollar}JAVA_HOME/bin/java -cp /path/to/log4j-api-${Log4jReleaseVersion}.jar:/path/to/log4j-core-${Log4jReleaseVersion}.jar:/path/to/log4j-jmx-gui-${Log4jReleaseVersion}.jar org.apache.logging.log4j.jmx.gui.ClientGui <options></code></p>
<p>or on Windows:</p>
- <p><code>%JAVA_HOME%\bin\java -cp \path\to\log4j-api-${project.version}.jar;\path\to\log4j-core-${project.version}.jar;\path\to\log4j-jmx-gui-${project.version}.jar org.apache.logging.log4j.jmx.gui.ClientGui <options></code></p>
+ <p><code>%JAVA_HOME%\bin\java -cp \path\to\log4j-api-${Log4jReleaseVersion}.jar;\path\to\log4j-core-${Log4jReleaseVersion}.jar;\path\to\log4j-jmx-gui-${Log4jReleaseVersion}.jar org.apache.logging.log4j.jmx.gui.ClientGui <options></code></p>
<p>Where <code>options</code> are one of the following:</p>
<ul>
<li><code><host>:<port></code></li>
@@ -155,9 +155,9 @@ com.sun.management.jmxremote.ssl=false</pre>
Monitoring and Management</a> provides details on how to configure
JMX more securely with password authentication and SSL.)</b></p>
<p>Then you can run the client with this command:</p>
- <p><code>$JAVA_HOME/bin/java -cp /path/to/log4j-api-${project.version}.jar:/path/to/log4j-core-${project.version}.jar:/path/to/log4j-jmx-gui-${project.version}.jar org.apache.logging.log4j.jmx.gui.ClientGui localhost:33445</code></p>
+ <p><code>${dollar}JAVA_HOME/bin/java -cp /path/to/log4j-api-${Log4jReleaseVersion}.jar:/path/to/log4j-core-${Log4jReleaseVersion}.jar:/path/to/log4j-jmx-gui-${Log4jReleaseVersion}.jar org.apache.logging.log4j.jmx.gui.ClientGui localhost:33445</code></p>
<p>or on Windows:</p>
- <p><code>%JAVA_HOME%\bin\java -cp \path\to\log4j-api-${project.version}.jar;\path\to\log4j-core-${project.version}.jar;\path\to\log4j-jmx-gui-${project.version}.jar org.apache.logging.log4j.jmx.gui.ClientGui localhost:33445</code></p>
+ <p><code>%JAVA_HOME%\bin\java -cp \path\to\log4j-api-${Log4jReleaseVersion}.jar;\path\to\log4j-core-${Log4jReleaseVersion}.jar;\path\to\log4j-jmx-gui-${Log4jReleaseVersion}.jar org.apache.logging.log4j.jmx.gui.ClientGui localhost:33445</code></p>
<p>The screenshot below shows the StatusLogger panel of the client
GUI when running as a stand-alone application.</p>
<p><img src="../images/jmx-standalone-statuslogger.png" alt="JMX GUI screenshot of StatusLogger display" /></p>