Index: RunRules.html
===================================================================
--- RunRules.html	(revision 1138292)
+++ RunRules.html	(working copy)
@@ -26,10 +26,10 @@
 	</STYLE>
 </HEAD>
 <BODY LANG="en-US" DIR="LTR">
-<H1 ALIGN=CENTER>Running the JDO 3.0 Technology Compatibility Kit</H1>
+<H1 ALIGN=CENTER>Running the JDO 3 Technology Compatibility Kit</H1>
 <P ALIGN=CENTER><BR><BR>
 </P>
-<P ALIGN=CENTER>24-May-2010</P>
+<P ALIGN=CENTER>7-July-2011</P>
 <P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Overview</FONT></FONT></P>
 <P>In order to demonstrate compliance with the Java Data Objects
 specification, an implementation must successfully run all of the TCK
@@ -42,11 +42,11 @@
 configuration information and test results. For an example of the
 required posting, please see <A HREF="http://db.apache.org/jdo/tck/final">http://db.apache.org/jdo/tck/final</A>.</P>
 <P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Prerequisites</FONT></FONT></P>
-<P>In order to run the TCK, you must install maven 1.x.x.
+<P>In order to run the TCK, you must install maven 2.x.x.
 M<FONT FACE="Times New Roman, serif">aven
-</FONT><A HREF="http://maven.apache.org/maven-1.x/"><FONT FACE="Times New Roman, serif"><FONT COLOR="#000000">http://maven.apache.org/maven-1.x/
+</FONT><A HREF="http://maven.apache.org/docs/2.2.1/release-notes.html"><FONT FACE="Times New Roman, serif"><FONT COLOR="#000000">http://maven.apache.org/docs/2.2.1/release-notes.html
 </FONT></FONT></A><FONT FACE="Times New Roman, serif">is the</FONT>
-driver of the test programs. Note that Maven 2 is not supported.</P>
+driver of the test programs. Note that Maven 3 is not supported.</P>
 <P>You must test the IUT on all configurations that the IUT supports.
 This includes different hardware and operating systems, different
 versions of Java, and different datastores. The TCK supports Java
@@ -130,12 +130,8 @@
 <P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Modifying
 the Configuration</FONT></FONT></P>
 <P>The Implementation Under Test (IUT) can be installed into the
-iut_jars directory in the TCK directory. Any .jar files in this
+lib/iut directory above the TCK directory. Any .jar files in this
 directory are added to the class path used to run the tests.</P>
-<P>There are properties in the build.properties file in the TCK
-directory that must be changed to configure the IUT execution and
-enhancement (optional) environment. These properties begin with
-iut.runtck and iut.enhancer. 
 </P>
 <P>There is are three properties files that must be modified to be
 IUT-specific, all located in the TCK src/conf directory. The
@@ -152,12 +148,12 @@
 <P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Running
 the Tests</FONT></FONT></P>
 <P>From the installation directory, change to the TCK directory. From
-the TCK directory, call &quot;maven build&quot; which will build the
+the TCK directory, call &quot;mvn integration-test&quot; which will build the
 jar files used in the tests, create the Derby database, install the
 schema into the Derby database, and run the TCK on the Reference
 Implementation. Success indicates that the TCK was installed
 correctly.</P>
-<P>Then call &quot;maven runtck.iut&quot; to run the tests on the
+<P>Then call &quot;mvn -Djdo.tck.impl=iut runtck&quot; to run the tests on the
 Implementation Under Test. This will produce console output plus a
 directory in the TCK/target/logs directory whose name contains the
 date/time the tests were started. This directory contains the output
@@ -167,7 +163,7 @@
 simultaneously.</P>
 <P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Debugging
 the IUT while Running TCK tests</FONT></FONT></P>
-<P>Execute &quot;maven help&quot; in the TCK directory in order to
+<P>Execute &quot;mvn jdo-exectck:help&quot; in the TCK directory in order to
 get information on running the TCK tests with a debugger. In
 particular, properties jdo.tck.cleanupaftertest, jdo.tck.cfglist,
 jdo.tck.identitytypes, and jdo.tck.dblist may be useful.</P>
