Mailing-List: contact jdo-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <20050623192623.14672.qmail@minotaur.apache.org>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r193206 - /incubator/jdo/trunk/README.txt
Date: Thu, 23 Jun 2005 19:26:23 -0000
To: jdo-commits@db.apache.org
From: mcaisse@apache.org

Author: mcaisse
Date: Thu Jun 23 12:26:21 2005
New Revision: 193206

URL: http://svn.apache.org/viewcvs?rev=193206&view=rev
Log:
info in README.txt on new maven goals/options

Modified:
    incubator/jdo/trunk/README.txt

Modified: incubator/jdo/trunk/README.txt
URL: http://svn.apache.org/viewcvs/incubator/jdo/trunk/README.txt?rev=193206&r1=193205&r2=193206&view=diff
==============================================================================
--- incubator/jdo/trunk/README.txt (original)
+++ incubator/jdo/trunk/README.txt Thu Jun 23 12:26:21 2005
@@ -156,11 +156,56 @@
 
 - See Prerequisites concerning JPOX and Derby.
 
-- Select test configuration (application or datastore) in project.properties, as described above.
+- Run "maven build" to build the tck.  This will compile, enhance, install the schemas, and run all the tests on all supported databases and identitytypes.
 
-- Run "maven build" to build the tck.  This will run all the tests.
+You may use the following custom goals and command line options
+with tck20/maven:
 
-- Run "maven runtck.jdori" to run all tests or "maven -Dtest=<test name> runtck.jdorisingle to run one test, e.g. transactions.Commit.
+Custom Goals:
+    * runtck.jdori - runs the TCK on the JDO Reference Implementation
+    * runtck.iut - runs the TCK on the implementation under test
+    * installSchema - installs the database schema
+    * enhance.jdori - enhances the class files using the JDO RI enhancer
+    * enhance.iut - enhances the class files using the
+                    implementation under test's enhancer
+
+Command Line Options:
+    -Djdo.tck.cfglist=<configuration file list>
+          Overrides test/conf/configuration.list by supplying
+          one or more space-separated test configuration files
+
+      -Djdo.tck.dblist=<database list>
+          Overrides the property value in project.properties by supplying
+          one or more space-separated database names
+
+      -Djdo.tck.identitytypes=<identity type list>
+            Overrides the property value in project.properties by supplying
+            one or more space-separated identity types (applicationidentity
+            or datastoreidentity) to use for this run.
+
+
+Maven looks for the following configuration files in test/conf:
+    * configurations.list
+          A list of files. Each file listed is a test configuration file.
+    * test configuration files
+          Each of these files sets values for
+                jdo.tck.testdescription - an optional string describing
+                    the purpose of these tests
+                jdo.tck.classes - a list of one or more test classes.
+                jdo.tck.testdata - fully qualified file name
+                    (not required by all tests)
+                jdo.tck.standarddata - fully qualified file name
+                    (not required by all tests)
+                jdo.tck.mapping - file designator that maven.xml uses
+                    to build a javax.jdo.option.Mapping value and
+                    corresponding schema name
+    * exclude.list
+          A list of test classes NOT to execute during a TCK test run
+          [Not yet fully implemented]
+
+For example, run "maven runtck.jdori" to run all tests or
+"maven -Djdo.tck.cfg=<configuration file name> runtck.jdori"
+to run one configuration.
 
 (6) Logging
 Apache JDO uses the apache commons logging package for logging.