You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by cl...@apache.org on 2021/05/07 23:11:56 UTC
[db-jdo] 14/43: JDO-366 Updated RunRules.html
This is an automated email from the ASF dual-hosted git repository.
clr pushed a commit to branch origin/2.0.1
in repository https://gitbox.apache.org/repos/asf/db-jdo.git
commit 534c7d12e25048e4e2f6f36c91d6f888ad8537c0
Author: Craig L Russell <cl...@apache.org>
AuthorDate: Thu Apr 13 23:19:02 2006 +0000
JDO-366 Updated RunRules.html
---
tck20/RunRules.html | 80 ++++++++++++++++++++++++++---------------------------
1 file changed, 40 insertions(+), 40 deletions(-)
diff --git a/tck20/RunRules.html b/tck20/RunRules.html
index 97a3865..ec39205 100644
--- a/tck20/RunRules.html
+++ b/tck20/RunRules.html
@@ -2,10 +2,10 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
- <TITLE></TITLE>
+ <TITLE>JDO 2.0 Technology Compatibility Kit Run Rules</TITLE>
<META NAME="GENERATOR" CONTENT="NeoOffice/J 1.1 (Unix)">
<META NAME="CREATED" CONTENT="20051228;16322200">
- <META NAME="CHANGED" CONTENT="20060331;15262300">
+ <META NAME="CHANGED" CONTENT="20060412;21332100">
<STYLE>
<!--
@page { size: 8.5in 11in }
@@ -16,12 +16,13 @@
<H1 ALIGN=CENTER>Running the JDO 2.0 Technology Compatibility Kit</H1>
<P ALIGN=CENTER><BR><BR>
</P>
-<P ALIGN=CENTER>30-Mar-2006</P>
+<P ALIGN=CENTER>13-Apr-2006</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
-tests that are not on the “excluded” list. The implementation is
-hereinafter referred to as the IUT (Implementation Under Test).</P>
+tests that are not on the "excluded" list. The
+implementation is hereinafter referred to as the IUT (Implementation
+Under Test).</P>
<P>The results must be posted on a publicly accessible web site for
examination by the public. The posting includes the output of the
test run, which consists of multiple log files containing
@@ -38,8 +39,7 @@ This includes different hardware and operating systems, different
versions of Java, and different datastores. The TCK supports Java
versions from JDK 1.3 to 1.5.</P>
<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Installation</FONT></FONT></P>
-<P>Download the zip file from the distribution at the Java Community
-Process web site http://jcp.org/en/jsr/detail?id=243. Unpack the zip
+<P>Download the zip file from the distribution location. Unpack the zip
file into a directory of your choice. In this directory you will
find:
</P>
@@ -50,8 +50,8 @@ find:
<LI><P>maven configuration files project.properties and project.xml
(common project definition for all Apache JDO projects including
the TCK). These files must not be changed.</P>
- <LI><P STYLE="margin-bottom: 0.2in">lib – this directory contains
- a directory ext that should contain jar fi<FONT FACE="Times New Roman, serif">les
+ <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
<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
@@ -65,44 +65,44 @@ find:
<LI><P>the TCK directory, which has a release-specific name (e.g.
jdo2-tck-2.0) and contains:</P>
<UL>
- <LI><P>maven.xml, project.properties, project.xml – the maven
+ <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
+ <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>this RunRules.html</P>
- <LI><P>assertions – contains the assertions file identifying the
+ <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>
- <LI><P>iut_jars – this directory is where the JDO implementation
+ <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>
+ <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
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.</P>
- <LI><P>src – this directory contains the test configuration
- files and directories:</P>
+ <LI><P>src - this directory contains the test configuration files
+ and directories:</P>
<UL>
- <LI><P>testdata – this directory contains data (represented as
+ <LI><P>testdata - this directory contains data (represented as
.xml files) loaded into the datastore for tests. These files must
not be modified.</P>
- <LI><P>sql – this directory contains DDL to define the tables
+ <LI><P>sql - this directory contains DDL to define the tables
used in the tests. The files distributed must not be modified.
Files may be created for databases for which the DDL for the
database under test is not provided.
</P>
- <LI><P>jdo – this directory contains .jdo metadata files for
- the persistent classes used in the tests. These files must not be
+ <LI><P>jdo - this directory contains .jdo metadata files for the
+ persistent classes used in the tests. These files must not be
modified.</P>
- <LI><P>orm – this directory contains .orm metadata files to map
+ <LI><P>orm - this directory contains .orm metadata files to map
the persistent classes to the sql tables. These files must not be
modified except to add DDL-generation information (which is not
used by the TCK).</P>
- <LI><P>java – this directory contains the source code to the
- TCK tests. These files must not be modified.</P>
- <LI><P>conf – this directory contains the configuration
+ <LI><P>java - this directory contains the source code to the TCK
+ tests. These files must not be modified.</P>
+ <LI><P>conf - this directory contains the configuration
information for the test runs. The file iut-pmf.properties in
this directory must be changed to provide properties for the IUT
persistence manager factory. The file jndi.properties may be
@@ -134,12 +134,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 “maven build” which will build the jar
-files used in the tests, create the Derby database, install the
+the TCK directory, call "maven build" 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 “maven runtck.iut” to run the tests on the
+<P>Then call "maven runtck.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
date/time the tests were started. This directory contains the output
@@ -148,10 +148,10 @@ of the tests. This is the directory to be published.</P>
20 instances of PersistenceManager with open transactions
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 “maven help” 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,
+the IUT while Running TCK tests</FONT></FONT></P>
+<P>Execute "maven help" 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>
<P>If you make a change to the IUT enhancer while debugging the TCK
tests (for implementations that use an enhancer) you must remove the
@@ -165,13 +165,13 @@ unmodified directory is the self-certification of the successful TCK
test run.</P>
<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>First
Level TCK Appeals Process</FONT></FONT></P>
-<P STYLE="margin-top: 0.17in; page-break-after: avoid">If any test
-does not pass on the JDO implementation under test, this may be due
-to an error in the implementation or in the TCK test. If you believe
-that the failure is due to an error in the TCK test, you may
+<P ALIGN=LEFT STYLE="margin-top: 0.17in; page-break-after: avoid">If
+any test does not pass on the JDO implementation under test, this may
+be due to an error in the implementation or in the TCK test. If you
+believe that the failure is due to an error in the TCK test, you may
challenge the test. To do so, send email to: <A HREF="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</A>
-with a subject line containing “CHALLENGE” and the name of the
-test program, e.g.
+with a subject line containing "CHALLENGE" and the name of
+the test program, e.g.
org.apache.jdo.tck.api.persistencemanager.ThreadSafe.java; and the
body of the email containing the details of the challenge.</P>
<P>The Maintenance Lead will respond within 15 working days with a
@@ -188,4 +188,4 @@ the Maintenance Lead, and a majority of votes cast will decide the
issue. The Maintenance Lead has one vote, as does each member of the
expert group at the time of the vote.</P>
</BODY>
-</HTML>
\ No newline at end of file
+</HTML>