jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fschumac...@apache.org
Subject svn commit: r1768721 - in /jmeter/trunk: docs/building.html docs/changes.html xdocs/building.xml
Date Tue, 08 Nov 2016 16:25:16 GMT
Author: fschumacher
Date: Tue Nov  8 16:25:16 2016
New Revision: 1768721

URL: http://svn.apache.org/viewvc?rev=1768721&view=rev
Log:
Add p tags to text nodes, so that they get rendered by vsl-templates.

Modified:
    jmeter/trunk/docs/building.html
    jmeter/trunk/docs/changes.html
    jmeter/trunk/xdocs/building.xml

Modified: jmeter/trunk/docs/building.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/building.html?rev=1768721&r1=1768720&r2=1768721&view=diff
==============================================================================
--- jmeter/trunk/docs/building.html (original)
+++ jmeter/trunk/docs/building.html Tue Nov  8 16:25:16 2016
@@ -53,25 +53,32 @@ The basic command is:</p>
 <pre class="source">
 ant [install]
 </pre>
+<p>
 See <span class="code">build.xml</span> (or call <span class="code">ant
-p</span>) for the other targets that can be used.
-
+</p>
 </div><div class="section"><h1>Contributing to JMeter</h1>
 <h2>We love contribution</h2>
+<p>
 We are very grateful to you if you take some time to contribute to the project.
 If you have some time to spend on the project you can pick existing enhancement or bug from
<a target="_blank" href="issues.html">Issues page</a>.<br>
 You can also contribute to translation, see <a href="localising/index.html">JMeter
Localisation (Translator's Guide)</a>.
+</p>
 
 <h2>Submitting a patch</h2>
-
+<p>
 If you want to contribute to JMeter for a bug fix or enhancement, here is the procedure to
follow:
+</p>
 
 <h3>Check your patch</h3>
+<p>
 Before submitting your patch ensure you do the following:<br>
 
 Check that patch compiles and follows Tab space policy by running:
+</p>
 <pre class="source">ant package-and-check</pre>
-
+<p>
 Check that patch does not break JUnit tests by running:
+</p>
 <pre class="source">ant test</pre>
 
 <h3>Create a PR using GIT</h3>

Modified: jmeter/trunk/docs/changes.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/changes.html?rev=1768721&r1=1768720&r2=1768721&view=diff
==============================================================================
--- jmeter/trunk/docs/changes.html (original)
+++ jmeter/trunk/docs/changes.html Tue Nov  8 16:25:16 2016
@@ -17,8 +17,9 @@ Earlier changes are detailed in the <a h
 
 
 <h1>Version 3.1</h1>
-
+<p>
 Summary
+</p>
 <ul>
 <li><a href="#New and Noteworthy">New and Noteworthy</a></li>
 <li><a href="#Incompatible changes">Incompatible changes</a></li>
@@ -33,7 +34,9 @@ Summary
 <h2 class="ch_section" id="New and Noteworthy">New and Noteworthy</h2>
 
 <h2 class="ch_section" id="Improve Report/Dashboard">Improve Report/Dashboard</h2>
+<p>
 The Dashboard has been improved with 3 new graphs and 1 summary table:
+</p>
 <ul>
     <li>Connect Time over Time graph : <figure><a href="./images/screenshots/dashboard/report_connect_time_over_time.png"><img
src="./images/screenshots/dashboard/report_connect_time_over_time.png" width="1635" height="520"
alt=""></a><figcaption></figcaption></figure></li>
     <li>Response Time Percentiles Over Time (successful responses) graph : <figure><a
href="./images/screenshots/dashboard/response_time_percentiles_over_time.png"><img src="./images/screenshots/dashboard/response_time_percentiles_over_time.png"
width="1640" height="539" alt=""></a><figcaption></figcaption></figure></li>
@@ -45,22 +48,32 @@ The Dashboard has been improved with 3 n
 </ul>
 
 <h2 class="ch_section" id="New Metrics">New Metrics</h2>
+<p>
 A new <span class="code">sent_bytes</span> metric has been introduced which reports
the bytes sent to server.<br>
 Another metric <span class="code">connect_time</span> has been enabled by default
in this version
+</p>
 
 <h2 class="ch_section" id="Handling Big responses">Handling Big responses</h2>
+<p>
 JMeter is now able to handle in terms of metrics responses bigger than 2GB, limit has been
increased to 9223372 TB.<br>
 To handle such big responses, it can also now truncate part of the response to avoid overflooding
memory. See <span class="code">httpsampler.max_bytes_to_store_per_request</span>
property.
+</p>
 
 <h2 class="ch_section" id="New __groovy function">New <span class="code">__groovy</span>
function</h2>
+<p>
 Introduce a new function <span class="code">__groovy</span> that enables Groovy
functions. This can be handy, as JavaScript can be quite slow (same for BeanShell), when used
in highly concurrent test plans.
+</p>
 
 <h2 class="ch_section" id="Use Groovy as default for JSR-223 elements">Use Groovy as
default for JSR-223 elements</h2>
+<p>
 Groovy is now set as the default language for JSR-223 elements. If you want to use another
of the supported language, you have to make an explicit choice.
+</p>
 <div class="clear"></div><div class="note">By default <span class="code">Cache
compiled script if available</span> is not checked by default although we advise you
to check it and ensure you don't use <span class="code">${varName}</span> syntax
to access JMeter variables but <span class="code">vars.get("varName")</span> instead.</div><div
class="clear"></div>
 
 <h2 class="ch_section" id="Formatted HTML source view in Results Tree View">Formatted
HTML source view in Results Tree View</h2>
+<p>
 The HTML source code in the Results Tree View can now be viewed formatted. This is extremely
useful, if the code of the webpage has been stripped of all superfluous whitespace.
+</p>
 <figure><a href="./images/screenshots/html-formatted-tree-view.png"><img src="./images/screenshots/html-formatted-tree-view.png"
width="635" height="271" alt="New formatted HTML source view"></a><figcaption>New
formatted HTML source view</figcaption></figure>
 
 <h3 class="ch_title">Core improvements</h3>
@@ -585,9 +598,7 @@ The HTML source code in the Results Tree
     -
   Since 2.13 (and <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=57514">
       Bug
-      57514</a>
-    -
-  ), Aggregate Graph, Summary Report and Aggregate Report lost precision in the Error, Rate
and Bandwidth values saved in the saved file csv</li>
+      57514</a>), Aggregate Graph, Summary Report and Aggregate Report lost precision
in the Error, Rate and Bandwidth values saved in the saved file csv</li>
 </ul>
 
 <h3>Timers, Assertions, Config, Pre- &amp; Post-Processors</h3>

Modified: jmeter/trunk/xdocs/building.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/building.xml?rev=1768721&r1=1768720&r2=1768721&view=diff
==============================================================================
--- jmeter/trunk/xdocs/building.xml (original)
+++ jmeter/trunk/xdocs/building.xml Tue Nov  8 16:25:16 2016
@@ -76,27 +76,34 @@ The basic command is:</p>
 <source>
 ant [install]
 </source>
+<p>
 See <code>build.xml</code> (or call <code>ant -p</code>) for the
other targets that can be used.
-
+</p>
 </section>
 
 <section name="Contributing to JMeter">
 <h2>We love contribution</h2>
+<p>
 We are very grateful to you if you take some time to contribute to the project.
 If you have some time to spend on the project you can pick existing enhancement or bug from
<a target="_blank" href="issues.html">Issues page</a>.<br/>
 You can also contribute to translation, see <a href="localising/index.html">JMeter
Localisation (Translator's Guide)</a>.
+</p>
 
 <h2>Submitting a patch</h2>
-
+<p>
 If you want to contribute to JMeter for a bug fix or enhancement, here is the procedure to
follow:
+</p>
 
 <h3>Check your patch</h3>
+<p>
 Before submitting your patch ensure you do the following:<br/>
 
 Check that patch compiles and follows Tab space policy by running:
+</p>
 <source>ant package-and-check</source>
-
+<p>
 Check that patch does not break JUnit tests by running:
+</p>
 <source>ant test</source>
 
 <h3>Create a PR using GIT</h3>



Mime
View raw message