Index: README.html =================================================================== --- README.html (revision 1578549) +++ README.html (working copy) @@ -46,9 +46,11 @@
JDO releases may be downloaded from the Apache JDO downloads page. @@ -89,21 +91,21 @@ MAVEN_OPTS.
-The JNDI test cases in tck need a JNDI implementation. The TCK is configured to use Sun's JNDI implementation. To use your own implementation, put the implementation -jar files into tck/lib/ext and update jndi.properties in the TCK directory -src/conf. To download Sun's implementation, go to -http://java.sun.com/products/jndi/downloads/index.html, -click the Download button at Download JNDI 1.2.1 & More, accept a license -agreement, download File System Service Provider, 1.2 Beta 3 and then unpack -the downloaded zip into tck/lib/ext. It includes the jars fscontext.jar and providerutil.jar. +jar files into lib/ext and update jndi.properties in the TCK directory +src/conf. To download Oracle's implementation, go to + + http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-java-plat-419418.html#7110-jndi-1.2.1-oth-JPR. +Aaccept the license agreement and download File System Service Provider, 1.2 Beta 3 and then unpack +the downloaded zip into lib/ext. It includes the jars fscontext.jar and providerutil.jar.
-To build the API, change to the "api" directory of the branch you are working in (or trunk) and run
mvn clean install-This will build the jdo-api artifact and install it in your local Maven2 repository. +This will build the jdo-api artifact and install it in your local Maven2 repository and +run the TCK on the Reference Implementation. -
-To run the JDO TCK on the Reference Implementation, copy the following files to the top-level -lib/jdori directory. Copy log4j.properties from tck/src/conf. The others may be downloaded from the maven repository. -
-Then change to the "exectck" directory of the branch you are working in (or trunk) and run -
mvn clean installThis builds and installs the "jdo-exectck" Maven plugin in your -local Maven2 repository. +to the top-level lib/iut directory, as well as log4j.properties and log4j-1.2.13.jar. +The log4j jar file may be copied from lib/jdori.
Change to the "tck" directory of the branch you are working in (or trunk) and run -
mvn clean installand this will run the TCK (via the "jdo-exectck" plugin) on the JDO Reference Implementation on all -supported databases and identity types. +
mvn -Djdo.tck.impl="iut" clean installand this will run the TCK +(via the "jdo-exectck" plugin) on the Implementation Under Test +on all supported databases and identity types.
The "jdo-exectck" plugin has various options so you can run other implementations or Index: tck/RunRules.html =================================================================== --- tck/RunRules.html (revision 1578549) +++ tck/RunRules.html (working copy) @@ -18,7 +18,7 @@
-
24-May-2010
@@ -52,47 +52,36 @@ versions of Java, and different datastores. The TCK supports Java versions 1.5 to 1.6.Installation
-Download the zip file from the distribution location. Unpack the zip -file into a directory of your choice. In this directory you will -find: +
Download the jdo.3.x-src.zip or jdo.3.x-src.gz file from the distribution location. Unpack the archive file into a directory of your choice. +Follow the instructions in the root level README.html file for building and running the JDO TCK. +Please take note of the following files:
README.html
Maven configuration file "pom.xml" - (common project definition for all Apache JDO projects including - the TCK). This file must not be changed.
-lib - this directory - contains a directory ext that should contain jar files - fscontext.jar and providerutil.jar used - by the JNDI tests. The - jar files can be found at - http://java.sun.com/products/jndi/downloads/index.html. - Choose "File System Service Provider, 1.2 Beta 3" from - the "Download JNDI 1.2.1 & More" page. Unzip the - archive and install them into the lib/ext directory. It is - permitted to use a different JNDI implementation; see the - README.txt for information on how to configure a different JNDI - implementation.
-the TCK directory, which has a release-specific name (e.g. - jdo-tck-3.1) and contains:
+ in the top level directory and subprojects. + These files must not be changed. +lib/ext - + Copy the jar files fscontext.jar and providerutil.jar used by the JNDI tests + into this directory. + It is permitted to use a different JNDI implementation; see + README.html for more information. +
+lib/iut - this directory is where the JDO implementation + jars are installed. It is empty in the distribution. To use the + 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 + files.
+the TCK directory, which contains:
pom.xml - the Maven definition of the project. - This file must not be modified.
-this RunRules.html
assertions - contains the assertions file identifying the assertions tested by the tests. This is for reference.
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 process.
-iut_jars - this directory is where the JDO implementation - jars are installed. It is empty in the distribution. To use the - 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 - files.
src - this directory contains the test configuration files and directories:
Modifying the Configuration
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. Any jar files in this directory are added to the class path used to run the tests.
There are properties in the build.properties file in the TCK directory that must be changed to configure the IUT execution and @@ -149,15 +138,10 @@ by the JDO implementation under test.
Running the Tests
-From the installation directory, change to the TCK directory. From -the TCK directory, call "mvn clean install" 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.
-Then call "mvn clean -Djdo.tck.impl="iut"" 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 +
Follow the instructions in README.html for running the TCK on the JDO Reference Implementation +and 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 of the tests. This is the directory to be published.
Some of the TCK tests require the implementation to support up to
Index: tck/pom.xml
===================================================================
--- tck/pom.xml (revision 1578549)
+++ tck/pom.xml (working copy)
@@ -1,8 +1,7 @@
-