deltaspike-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r946334 - in /websites/staging/deltaspike/trunk/content: ./ documentation/test-control.html
Date Sat, 04 Apr 2015 20:23:32 GMT
Author: buildbot
Date: Sat Apr  4 20:23:31 2015
New Revision: 946334

Log:
Staging update by buildbot for deltaspike

Modified:
    websites/staging/deltaspike/trunk/content/   (props changed)
    websites/staging/deltaspike/trunk/content/documentation/test-control.html

Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Apr  4 20:23:31 2015
@@ -1 +1 @@
-1671309
+1671310

Modified: websites/staging/deltaspike/trunk/content/documentation/test-control.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/test-control.html (original)
+++ websites/staging/deltaspike/trunk/content/documentation/test-control.html Sat Apr  4 20:23:31
2015
@@ -484,7 +484,7 @@ To pass properties to the underlying tes
 you have to add <code>/META-INF/apache-deltaspike_test-container.properties</code>
 to the resources-directory of your test-classpath.
 The content of the file are key/value pairs which get passed to the container.
-Therefore, it is a configuration which isis not used by DeltaSpike itself
+Therefore, it is a configuration which is not used by DeltaSpike itself
 (it is just forwarded (as it is) to the underlying test-container).</p>
 </div>
 <div class="sect3">
@@ -521,7 +521,7 @@ easier. Therefore it is possible to crea
 via a mocking framework and add them, for example, via <code>DynamicMockManager</code>.</p>
 </div>
 <div class="paragraph">
-<p><strong>Attention:</strong> Mocking CDI beans isis not supported for
every feature of CDI and/or
+<p><strong>Attention:</strong> Mocking CDI beans is not supported for every
feature of CDI and/or
 every implementation version. For example, we cais not mock intercepted CDI beans and
 with some implementations mocking specialized beans fails.
 Usually all features are active by default, however,
@@ -857,7 +857,7 @@ with:</p>
 <h4 id="_liquibase">Liquibase</h4>
 <div class="paragraph">
 <p>Liquibase invokes <code>#toString</code> in a <code>AfterDeploymentValidation</code>
observer.
-<strong>that isis not portable</strong> and therefore you have to deactivate
the
+<strong>that is not portable</strong> and therefore you have to deactivate the
 mocking-support via:</p>
 </div>
 <div class="listingblock">



Mime
View raw message