db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From m..@apache.org
Subject svn commit: r949389 - in /db/jdo/trunk: README.html tck/RunRules.html
Date Sat, 29 May 2010 13:53:15 GMT
Author: mbo
Date: Sat May 29 13:53:15 2010
New Revision: 949389

URL: http://svn.apache.org/viewvc?rev=949389&view=rev
Log:
JDO 3 changes in Readme and RunRules

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

Modified: db/jdo/trunk/README.html
URL: http://svn.apache.org/viewvc/db/jdo/trunk/README.html?rev=949389&r1=949388&r2=949389&view=diff
==============================================================================
--- db/jdo/trunk/README.html (original)
+++ db/jdo/trunk/README.html Sat May 29 13:53:15 2010
@@ -18,10 +18,10 @@
 <HTML>
 <HEAD>
 	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
-	<TITLE>JDO 2 TCK README</TITLE>
+	<TITLE>JDO 3 TCK README</TITLE>
 </HEAD>
 <BODY LANG="en-US" DIR="LTR">
-<H1>The JDO 2 Technology Compatibility Kit</H1>
+<H1>The JDO 3 Technology Compatibility Kit</H1>
 <UL>
     <LI><a href="#overview">Overview</a></LI>
     <!-- For minor release change documentation
@@ -43,23 +43,19 @@
     </UL></LI>
     </UL>
 <a name="overview"></a>
-<H2>Overview of the JDO 2 Technology Compatibility Kit</H2>
+<H2>Overview of the JDO 3 Technology Compatibility Kit</H2>
 <p>
-The JDO 2 project includes the JDO 2 TCK and its dependencies:
+The JDO 3 project includes the JDO 3 TCK and its dependencies:
 </p>
 <UL>
-    <LI>api2 contains source to build jdo2-api-2.3.jar, which defines the JDO API version
2.3 for Java 1.5 and later.</LI>
-    <LI>api2-legacy contains source to build jdo2-api-legacy-2.3.jar, which defines
the JDO API version 2.3 for Java 1.4 and earlier. *** THIS IS DEPRECATED IN JDO2.3+</LI>
-    <LI>core20 contains the JDO2 core, including utility and metadata model classes</LI>
-    <LI>enhancer20 contains the utility classes used for verifying enhanced files</LI>
-    <LI>tck2 contains the JDO 2.3 Technology Compatibility Kit for Java 1.5 and later.</LI>
-  <LI>tck2-legacy contains the JDO 2.3 Technology Compatibility Kit for Java 1.4 and
earlier. *** THIS IS DEPRECATED IN JDO2.3+</LI>
+    <LI>api contains source to build jdo-api-3.0.jar, which defines the JDO API version
3.0 for Java 1.5 and later.</LI>
+    <LI>tck contains the JDO 3.0 Technology Compatibility Kit for Java 1.5 and later.</LI>
 </UL>
 <p>
 JDO releases may be downloaded from <a href="http://db.apache.org/jdo/downloads.html">the
Apache JDO downloads page</a>. Minor updates of releases are only available as source
from the Subversion repository. Follow the instructions <a href="#building">below</a>
to build the TCK from source.
 <p>
 For complete rules for certifying a JDO implementation,
-see RunRules.html in the top level tck2 project directory.
+see RunRules.html in the top level tck project directory.
 </p>
 <!-- When creating a new minor release branch, list changes from the major release here

 
@@ -94,7 +90,7 @@ MAVEN_OPTS.
 Mevenide is a nice maven plugin for IDEs available from http://mevenide.codehaus.org.
 In Netbeans, after you install the plugin, you can open an 
 existing maven project by File -> Open Project -> Open Project Folder.
-Navigate to a directory including a maven project (e.g. api2) and choose this 
+Navigate to a directory including a maven project (e.g. api) and choose this 
 directory. Netbeans will create a project folder. If you right-click the Maven 
 project you can examine the contents of the project.xml (see Properties) or 
 execute goals.
@@ -102,7 +98,7 @@ execute goals.
 <a name="jndi"></a>
 <h3>JNDI implementation (fscontext.jar and providerutil.jar)</h3>
 <p>
-The JNDI test cases in tck2 need a JNDI implementation.
+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 lib/ext and update jndi.properties in the TCK directory
@@ -116,15 +112,11 @@ the downloaded zip. It includes the jars
 <h2>Building the TCK from Source</h2>
 For instructions for checking out the JDO source, see the Apache JDO <a href="http://db.apache.org/jdo/svn.html">source
code</a> page.
 <p>
-If you are using Java 1.5, before building, edit project.properties in the tck2 directory
to comment out the line that sets maven.compile.compilerargs:
-<pre>
-#maven.compile.compilerargs= -proc:none
-</pre>
 To build the TCK dependencies, change to the top level directory of the branch you are working
in (or trunk if you are using the latest unreleased code) and run
 <pre>
-maven tck2.default
+maven tck.default
 </pre>
-Then change to the "tck2" directory and run
+Then change to the "tck" directory and run
 <pre>
 maven build
 </pre>
@@ -133,13 +125,13 @@ When execution completes, you are ready 
 <a name="running"></a>
 <h2>Running the TCK</h2>
 <p>
-In the tck2 project, run "maven build" to build the tck.  This will 
+In the tck project, run "maven build" to build the tck.  This will 
 compile, enhance, install the schemas, and run all the tests on the RI on all 
 supported databases and identitytypes.
 </p>
 <p>
 You may use the following custom goals and command line options
-with the tck2 project:
+with the tck project:
 </p>
 <a name="goals"></a>
 <h3>Custom Goals</h3>
@@ -167,9 +159,9 @@ with the tck2 project:
 <a name="cli"></a>
     <h3>Command Line Options</h3>
     <DL>
-        <DT>-Djdo.tck.cfglist=<i>configuration file list</i><DD>Overrides
the definition of jdo.tck.cfglist found in tck2/src/conf/configuration.list by supplying one
or more space-separated test configuration files. Test configuration files typically have
the .conf extension. To run a single test, create a .conf file (copy an existing file) and
put the test into the jdo.tck.classes property.
-        <DT>-Djdo.tck.dblist=<i>database list</i><DD>Overrides the
property value in project.properties by supplying one or more space-separated database names
-        <DT>-Djdo.tck.identitytypes=<i>identity type list</i><DD>Overrides
the property value in project.properties by supplying one or more space-separated identity
types (applicationidentity or datastoreidentity) to use for this run.
+        <DT>-Djdo.tck.cfglist=<i>configuration file list</i><DD>Overrides
the definition of jdo.tck.cfglist found in tck/src/conf/configuration.list by supplying one
or more comma-separated test configuration files. Test configuration files typically have
the .conf extension. To run a single test, create a .conf file (copy an existing file) and
put the test into the jdo.tck.classes property.
+        <DT>-Djdo.tck.dblist=<i>database list</i><DD>Overrides the
property value in project.properties by supplying one or more comma-separated database names
+        <DT>-Djdo.tck.identitytypes=<i>identity type list</i><DD>Overrides
the property value in project.properties by supplying one or more comma-separated identity
types (applicationidentity or datastoreidentity) to use for this run.
         <DT>-Djdo.tck.cleanupaftertest=<i>boolean</i><DD>When false,
data is retained in the database after the test. This allows inspection of data after test
is run. Default is true.
         <DT>-Djdo.tck.debug.port=<i>port number</i><DD>Sets the port
number the JVM should listen for a debugger on. Default is 8787.
         <DT>-Djdo.tck.debug.jvmargs=<i>args</i><DD>Sets the "-Xdebug
..." arguments to allow you to supply your own debug directives.

Modified: db/jdo/trunk/tck/RunRules.html
URL: http://svn.apache.org/viewvc/db/jdo/trunk/tck/RunRules.html?rev=949389&r1=949388&r2=949389&view=diff
==============================================================================
--- db/jdo/trunk/tck/RunRules.html (original)
+++ db/jdo/trunk/tck/RunRules.html Sat May 29 13:53:15 2010
@@ -18,7 +18,7 @@
 <HTML>
 <HEAD>
 	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
-	<TITLE>JDO 2.3 Technology Compatibility Kit Run Rules</TITLE>
+	<TITLE>JDO 3.0 Technology Compatibility Kit Run Rules</TITLE>
 	<STYLE>
 	<!--
 		@page { size: 8.5in 11in }
@@ -26,10 +26,10 @@
 	</STYLE>
 </HEAD>
 <BODY LANG="en-US" DIR="LTR">
-<H1 ALIGN=CENTER>Running the JDO 2.3 Technology Compatibility Kit</H1>
+<H1 ALIGN=CENTER>Running the JDO 3.0 Technology Compatibility Kit</H1>
 <P ALIGN=CENTER><BR><BR>
 </P>
-<P ALIGN=CENTER>6-June-2008</P>
+<P ALIGN=CENTER>24-May-2010</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
@@ -76,7 +76,7 @@ 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.
-		jdo2-tck-2.1) and contains:</P>
+		jdo-tck-3.0) 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>



Mime
View raw message