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 2006/04/01 01:31:41 UTC
svn commit: r390542 - /db/jdo/branches/2.0/README.txt
Author: clr
Date: Fri Mar 31 15:31:40 2006
New Revision: 390542
URL: http://svn.apache.org/viewcvs?rev=390542&view=rev
Log:
JDO-356 Update README.txt
Modified:
db/jdo/branches/2.0/README.txt
Modified: db/jdo/branches/2.0/README.txt
URL: http://svn.apache.org/viewcvs/db/jdo/branches/2.0/README.txt?rev=390542&r1=390541&r2=390542&view=diff
==============================================================================
--- db/jdo/branches/2.0/README.txt (original)
+++ db/jdo/branches/2.0/README.txt Fri Mar 31 15:31:40 2006
@@ -1,4 +1,4 @@
-This is the release candidate 1 of the JDO 2 project. It includes
+This is the official release of the JDO 2 project. It includes
the JDO 2.0 TCK and its dependencies:
- api20 contains source to build jdo.jar, which defines the JDO API version 2.0
@@ -16,7 +16,7 @@
http://maven.apache.org/start/download.html
Note that maven uses the user.home system property for the location
-of the maven local repostitory: ${user.home}/.maven/repository.
+of the maven local repository: ${user.home}/.maven/repository.
Under Windows this system property is C:\Documents and Settings\<user>
no matter what the HOME variable is set to. As a workaround you may set the
system property by adding -Duser.home=%HOME% to the environment variable
@@ -34,7 +34,7 @@
the downloaded zip. It includes the jars fscontext.jar and providerutil.jar.
- JPOX
-The Reference Implementation for JDO 2.0 is JPOX. The tck20 subproject
+The Reference Implementation for JDO 2.0 is JPOX 1.1.0. The tck20 subproject
automatically downloads the JPOX jar files via maven configuration.
- derby
@@ -70,10 +70,10 @@
Running the TCK
-------
-This version of the TCK is almost final.
+This version of the TCK is final.
In the tck20 project, run "maven build" to build the tck. This will
-compile, enhance, install the schemas, and run all the tests on all
+compile, enhance, install the schemas, and run all the tests on the RI on all
supported databases and identitytypes.
You may use the following custom goals and command line options