You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by pm...@apache.org on 2016/01/03 23:32:35 UTC

svn commit: r1722766 - /jmeter/trunk/xdocs/usermanual/remote-test.xml

Author: pmouawad
Date: Sun Jan  3 22:32:35 2016
New Revision: 1722766

URL: http://svn.apache.org/viewvc?rev=1722766&view=rev
Log:
Clarify documentations by removing old versions mention

Modified:
    jmeter/trunk/xdocs/usermanual/remote-test.xml

Modified: jmeter/trunk/xdocs/usermanual/remote-test.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/remote-test.xml?rev=1722766&r1=1722765&r2=1722766&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/remote-test.xml (original)
+++ jmeter/trunk/xdocs/usermanual/remote-test.xml Sun Jan  3 22:32:35 2016
@@ -92,7 +92,7 @@ To revert to the previous behaviour, def
 </p>
 <p>
 By default, RMI uses a dynamic port for the JMeter server engine. This can cause problems for firewalls,
-so with versions of JMeter after 2.3.2 you can define the JMeter property <code>server.rmi.localport</code> 
+so with you can define the JMeter property <code>server.rmi.localport</code> 
 to control this port number.
 If this is non-zero, it will be used as the local port number for the server engine.
 </p>