[webbeans-commits] Webbeans SVN: r3068 - tck/trunk/doc/reference/en-US.

[webbeans-commits at lists.jboss.org]

Author: dan.j.allen
Date: 2009-07-16 19:33:04 -0400 (Thu, 16 Jul 2009)
New Revision: 3068

Modified:
   tck/trunk/doc/reference/en-US/executing.xml
Log:
add note about incontainer-debug profile


Modified: tck/trunk/doc/reference/en-US/executing.xml
===================================================================
--- tck/trunk/doc/reference/en-US/executing.xml	2009-07-16 19:20:03 UTC (rev 3067)
+++ tck/trunk/doc/reference/en-US/executing.xml	2009-07-16 23:33:04 UTC (rev 3068)
@@ -22,8 +22,10 @@
     <programlisting>&lt;webbeans_install_dir&gt;/jboss-as/local.build.properties</programlisting>
     <para>Then, add the <literal>incontainer</literal> property to the command that launches the Maven 2 life cycle:</para>
     <programlisting>mvn test -Dincontainer</programlisting>
-    <para>The presence of the <literal>incontainer</literal> property activates a Maven 2 profile that assigns the  <literal>org.jboss.testharness.standalone</literal> system property to <literal>false</literal> and the <literal>org.jboss.testharness.runIntegrationTests</literal> system property to <literal>true</literal>, hence activing the in-container test mode.</para>
-    <para>When the Maven 2 life cycle is run with the <literal>incontainer</literal> property present, all the test artifacts in the test suite are executed. The in-container mode uses the <literal>Containers</literal> SPI to deploy the test artifact to the container and execute the test in a true Java EE life cycle. The JBoss TCK runner has a dependency on the library that provides an implementation of this interface for JBoss AS 5.1.</para>
+    <para>The presence of the <literal>incontainer</literal> property activates a Maven 2 profile that assigns the  <literal>org.jboss.testharness.standalone</literal> system property to <literal>false</literal> and the <literal>org.jboss.testharness.runIntegrationTests</literal> system property to <literal>true</literal>, hence activing the in-container test mode. This time, all the test artifacts in the test suite are executed.</para>
+    <para>The in-container profile will also start and stop the application server automatically by setting the <literal>org.jboss.testharness.container.forceRestart</literal> to <literal>true</literal>. If you want to connect to an instance that is already running, activate in-container mode using the <literal>incontainer-debug</literal> command line property instead.</para>
+    <programlisting>mvn test -Dincontainer-debug</programlisting>
+    <para>The in-container mode uses the <literal>Containers</literal> SPI to deploy the test artifact to the container and execute the test in a true Java EE life cycle. The JBoss TCK runner has a dependency on the library that provides an implementation of this interface for JBoss AS 5.1.</para>
     <para>Since in-container tests are executed in a remote JVM, the results of the test must be communicated back to the runner over a container-supported protocol. The JBoss Test Harness provides servlet-based communication over HTTP as described in section 3.3.</para>
   </section>
   <section>