db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From an...@apache.org
Subject svn commit: r1243036 - /db/jdo/trunk/tck/RunRules.html
Date Sat, 11 Feb 2012 11:50:44 GMT
Author: andyj
Date: Sat Feb 11 11:50:44 2012
New Revision: 1243036

URL: http://svn.apache.org/viewvc?rev=1243036&view=rev
Log:
bring up to Maven2+ standard

Modified:
    db/jdo/trunk/tck/RunRules.html

Modified: db/jdo/trunk/tck/RunRules.html
URL: http://svn.apache.org/viewvc/db/jdo/trunk/tck/RunRules.html?rev=1243036&r1=1243035&r2=1243036&view=diff
==============================================================================
--- db/jdo/trunk/tck/RunRules.html (original)
+++ db/jdo/trunk/tck/RunRules.html Sat Feb 11 11:50:44 2012
@@ -42,11 +42,11 @@ test run, which consists of multiple log
 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
 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/"><FONT FACE="Times New Roman, serif"><FONT
COLOR="#000000">http://maven.apache.org/
 </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.</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
@@ -60,11 +60,11 @@ find: 
 	<UL>
 		<LI><P>README.html 
 		</P>
-		<LI><P>maven configuration files project.properties and project.xml
+		<LI><P>Maven configuration file "pom.xml"
 		(common project definition for all Apache JDO projects including
-		the TCK). These files must not be changed.</P>
+		the TCK). This file must not be changed.</P>
 		<LI><P ALIGN=LEFT STYLE="margin-bottom: 0.2in">lib - this directory
-		contains a directory ext that should contain jar fi<FONT FACE="Times New Roman, serif">les
+		contains a directory ext that should contain jar files<FONT FACE="Times New Roman, serif">
 		<FONT COLOR="#000000">fscontext.jar and providerutil.jar </FONT>us</FONT>ed
 		by the JNDI tests. <FONT FACE="Times New Roman, serif"><FONT COLOR="#000000">The
 		jar files can be found at
@@ -76,21 +76,19 @@ find: 
 		README.txt for information on how to configure a different JNDI
 		implementation.</FONT></FONT></P>
 		<LI><P>the TCK directory, which has a release-specific name (e.g.
-		jdo-tck-3.0) and contains:</P>
+		jdo-tck-3.1) and contains:</P>
 		<UL>
-			<LI><P>maven.xml, project.properties, project.xml - the maven
-			definition of the project. These files must not be modified.</P>
-			<LI><P>build.properties - the maven definition for the IUT. This
-			file may be modified to change any of the IUT properties needed.</P>
+			<LI><P>pom.xml - the Maven definition of the project.
+			This file must not be modified.</P>
 			<LI><P>this RunRules.html</P>
 			<LI><P>assertions - contains the assertions file identifying the
 			assertions tested by the tests. This is for reference.</P>
 			<LI><P>target - this directory contains artifacts of compiling and
 			running the tests. It does not exist in the distribution and will
-			be created by the maven build script.</P>
+			be created by the maven build process.</P>
 			<LI><P>iut_jars - this directory is where the JDO implementation
 			jars are installed. It is empty in the distribution. To use the
-			maven target runtck.iut (required for an implementation to prove
+			maven target runtck (required for an implementation to prove
 			compliance), copy the JDO implementation jar files into this
 			directory. Alternatively, update the build.properties file in the
 			TCK directory to refer to an existing location of the IUT jar
@@ -152,12 +150,12 @@ by the JDO implementation under test.</P
 <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 clean install&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 clean -Djdo.tck.impl="iut"&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 +165,7 @@ of the tests. This is the directory to b
 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>
@@ -197,7 +195,7 @@ decision on whether there is an error in
 is found by the Maintenance Lead to be due to an error in the test
 case, the Maintenance Lead might patch the erroneous test or add the test
 to the exclude list.
-The user can obtain the TCK updates by checking out the latest minor version branch, 2.n.1.
+The user can obtain the TCK updates by checking out the latest minor version branch, 3.n.1.
 If a fix is not provided within 15 working days of the receipt of the challenge,
 then the user may put the test into the TCK file src/conf/exclude.list and
 it will not be run as part of the TCK.</P>



Mime
View raw message