You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@db.apache.org by mc...@apache.org on 2013/01/21 05:23:18 UTC
svn commit: r847423 [13/14] - in /websites/production/db/content/jdo: ./
guides/ releases/
Modified: websites/production/db/content/jdo/releases/release-3.0.html
==============================================================================
--- websites/production/db/content/jdo/releases/release-3.0.html (original)
+++ websites/production/db/content/jdo/releases/release-3.0.html Mon Jan 21 04:23:17 2013
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 16, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 20, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Maven -
+ <title>JDO -
Apache JDO 3.0 Release</title>
<style type="text/css" media="all">
@import url("../css/maven-base.css");
@@ -12,7 +12,7 @@
</style>
<link rel="stylesheet" href="../css/print.css" type="text/css" media="print" />
<meta name="author" content="JDO Documentation Team" />
- <meta name="Date-Revision-yyyymmdd" content="20130116" />
+ <meta name="Date-Revision-yyyymmdd" content="20130120" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,13 @@
<div id="breadcrumbs">
- <div class="xright"> <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
+ <div class="xright"> <a href="https://www.facebook.com/JavaDataObjects" class="externalLink" title="Facebook">Facebook</a>
+ |
+ <a href="https://twitter.com/JavaDataObjects" class="externalLink" title="Twitter">Twitter</a>
+ |
+ <a href="https://plus.google.com/106584233526334524963" class="externalLink" title="Google+">Google+</a>
+ |
+ <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
|
<a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630" class="externalLink" title="Issue Tracker">Issue Tracker</a>
|
@@ -204,147 +210,147 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
-
-
- <div class="section"><h2>JDO 3.0 Distributions<a name="JDO_3.0_Distributions"></a></h2>
- <p>
- Use the links below to download Apache JDO from one of our mirrors.
- For more information about the projects see <a href="../downloads.html">Downloads</a>.
- For information on running the TCK, see <a href="../tck.html">TCK</a>.
- </p>
- <p>
- It is good practice to <a href="#Verifying">verify the integrity</a>
- of the distribution files.
- </p>
- <p>
- You are currently using <b>[preferred]</b>.
- If you encounter a problem with this mirror, then please select another.
- If all mirrors are failing, there are backup mirrors at the end of the list.
- See <a class="externalLink" href="http://www.apache.org/mirrors/">status</a> of mirrors.
- </p>
- <form action="[location]" method="get" id="SelectMirror">
- Other mirrors: <select name="Preferred">
- [if-any http]
- [for http]<option value="[http]">[http]</option>[end]
- [end]
- [if-any ftp]
- [for ftp]<option value="[ftp]">[ftp]</option>[end]
- [end]
- [if-any backup]
- [for backup]<option value="[backup]">[backup] (backup)</option>[end]
- [end]
- </select>
- <input type="submit" value="Change" />
- </form>
- <br />
-
- <div class="section"><h3>Release Notes<a name="Release_Notes"></a></h3>
- <p>
- <a class="externalLink" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12313404&styleName=Html&projectId=10630">
- View release notes for JDO 3.0</a>
- </p>
- </div>
- <div class="section"><h3>API<a name="API"></a></h3>
- <p>
- The api project contains source to build jdo-api.jar,
- which defines the JDO API.
- The jar file is the only artifact needed for users who wish to compile
- their programs using the JDO API.
- It can be downloaded automatically by maven and placed into the local
- maven repository if you include the
- proper dependency in your maven project definition.
- Use groupId javax.jdo, artifactId jdo-api, version 3.0
- and define your remote repository as
- http://www.ibiblio.org/maven.
- Alternatively, it can be downloaded manually and put into a location
- of your choice.
- </p>
- <p>
- <a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.jar">jdo-api-3.0.jar</a>
- [<a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.jar.asc">PGP</a>]
- [<a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.jar.md5">MD5</a>]
- </p>
- <p>
- <a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.pom">jdo-api-3.0.pom</a>
- [<a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.pom.asc">PGP</a>]
- [<a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.pom.md5">MD5</a>]
- </p>
- <p>
- <a href="[preferred]/db/jdo/3.0/jdo-api-3.0-src.zip">jdo-api-3.0-src.zip</a>
- [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-api-3.0-src.zip.asc">PGP</a>]
- [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-api-3.0-src.zip.md5">MD5</a>]
- </p>
- <p>
- <a href="[preferred]/db/jdo/3.0/jdo-api-3.0-src.tar.gz">jdo-api-3.0-src.tar.gz</a>
- [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-api-3.0-src.tar.gz.asc">PGP</a>]
- [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-api-3.0-src.tar.gz.md5">MD5</a>]
- </p>
- </div>
-
- <div class="section"><h3>TCK<a name="TCK"></a></h3>
- <p>
- This is a download for all implementors of JDO, and for those who want to check
- how well an implementation is compliant with the JDO specification.
- The tck2 project contains the JDO 2 Technology Compatibility Kit.
- The source distribution is the only artifact needed to be downloaded
- by the user. The dependencies (including the model20 jar,
- util20 jar, enhancer20 jar, api2 jar, and JPOX)
- are automatically downloaded by maven as needed to run the TCK.
-
- </p>
- <p>
- <a href="[preferred]/db/jdo/3.0/jdo-tck-3.0-src.zip">jdo-tck-3.0-src.zip</a>
- [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-tck-3.0-src.zip.asc">PGP</a>]
- [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-tck-3.0-src.zip.md5">MD5</a>]
- </p>
- <p>
- <a href="[preferred]/db/jdo/3.0/jdo-tck-3.0-src.tar.gz">jdo-tck-3.0-src.tar.gz</a>
- [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-tck-3.0-src.tar.gz.asc">PGP</a>]
- [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-tck-3.0-src.tar.gz.md5">MD5</a>]
- </p>
- </div>
-
- </div>
-
-<div class="section"><h2>Verifying Releases<a name="Verifying_Releases"></a></h2>
-<a name="Verifying"></a>
-<p>It is essential that you verify the integrity of the downloaded
-files using the PGP signature and/or the MD5 checksum. The
-checksum is not as strong an indicator as the PGP signature is.</p>
-<p>The PGP signatures can be verified using PGP or GPG.
-First download the <a class="externalLink" href="http://www.apache.org/dist/db/jdo/KEYS">KEYS</a>
-as well as the <tt>asc</tt> signature file for the particular
-distribution.
-Make sure you get these files from the
-<a class="externalLink" href="http://www.apache.org/dist/db/jdo/">main distribution
-directory</a>, rather than from a mirror. Then verify the signatures using
-</p>
-<p><tt>
-% pgpk -a KEYS<br />
-% pgpv <i>release_name</i>.tar.gz.asc<br />
-</tt>
-<i>or</i><br />
-<tt>
-% pgp -ka KEYS<br />
-% pgp <i>release_name</i>.tar.gz.asc<br />
-</tt>
-<i>or</i><br />
-<tt>
-% gpg --import KEYS<br />
-% gpg --verify <i>release_name</i>.tar.gz.asc
-</tt></p>
-<p>Alternatively, you can verify the checksums on the files. Unix
-programs called <tt>md5</tt>/<tt>sha1</tt> or
-<tt>md5sum</tt>/<tt>sha1sum</tt> are included in many unix
-distributions. <tt>*sum</tt> is also available as part of
-<a class="externalLink" href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>.
-Windows users can get binary md5 programs from <a class="externalLink" href="http://www.fourmilab.ch/md5/">http://www.fourmilab.ch/md5</a> and
-<a class="externalLink" href="http://www.pc-tools.net/win32/freeware/console/">hhttp://www.pc-tools.net/win32/freeware/console</a>.
-Windows SlavaSoft <a class="externalLink" href="http://www.slavasoft.com/fsum/">fsum</a> supports MD5 and
-SHA1.</p>
-<p>We highly recommend verifying the PGP signature, though.</p>
- </div>
-
+
+
+ <div class="section"><h2>JDO 3.0 Distributions<a name="JDO_3.0_Distributions"></a></h2>
+ <p>
+ Use the links below to download Apache JDO from one of our mirrors.
+ For more information about the projects see <a href="../downloads.html">Downloads</a>.
+ For information on running the TCK, see <a href="../tck.html">TCK</a>.
+ </p>
+ <p>
+ It is good practice to <a href="#Verifying">verify the integrity</a>
+ of the distribution files.
+ </p>
+ <p>
+ You are currently using <b>[preferred]</b>.
+ If you encounter a problem with this mirror, then please select another.
+ If all mirrors are failing, there are backup mirrors at the end of the list.
+ See <a class="externalLink" href="http://www.apache.org/mirrors/">status</a> of mirrors.
+ </p>
+ <form action="[location]" method="get" id="SelectMirror">
+ Other mirrors: <select name="Preferred">
+ [if-any http]
+ [for http]<option value="[http]">[http]</option>[end]
+ [end]
+ [if-any ftp]
+ [for ftp]<option value="[ftp]">[ftp]</option>[end]
+ [end]
+ [if-any backup]
+ [for backup]<option value="[backup]">[backup] (backup)</option>[end]
+ [end]
+ </select>
+ <input type="submit" value="Change" />
+ </form>
+ <br />
+
+ <div class="section"><h3>Release Notes<a name="Release_Notes"></a></h3>
+ <p>
+ <a class="externalLink" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12313404&styleName=Html&projectId=10630">
+ View release notes for JDO 3.0</a>
+ </p>
+ </div>
+ <div class="section"><h3>API<a name="API"></a></h3>
+ <p>
+ The api project contains source to build jdo-api.jar,
+ which defines the JDO API.
+ The jar file is the only artifact needed for users who wish to compile
+ their programs using the JDO API.
+ It can be downloaded automatically by maven and placed into the local
+ maven repository if you include the
+ proper dependency in your maven project definition.
+ Use groupId javax.jdo, artifactId jdo-api, version 3.0
+ and define your remote repository as
+ http://www.ibiblio.org/maven.
+ Alternatively, it can be downloaded manually and put into a location
+ of your choice.
+ </p>
+ <p>
+ <a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.jar">jdo-api-3.0.jar</a>
+ [<a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.jar.asc">PGP</a>]
+ [<a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.jar.md5">MD5</a>]
+ </p>
+ <p>
+ <a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.pom">jdo-api-3.0.pom</a>
+ [<a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.pom.asc">PGP</a>]
+ [<a class="externalLink" href="http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.pom.md5">MD5</a>]
+ </p>
+ <p>
+ <a href="[preferred]/db/jdo/3.0/jdo-api-3.0-src.zip">jdo-api-3.0-src.zip</a>
+ [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-api-3.0-src.zip.asc">PGP</a>]
+ [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-api-3.0-src.zip.md5">MD5</a>]
+ </p>
+ <p>
+ <a href="[preferred]/db/jdo/3.0/jdo-api-3.0-src.tar.gz">jdo-api-3.0-src.tar.gz</a>
+ [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-api-3.0-src.tar.gz.asc">PGP</a>]
+ [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-api-3.0-src.tar.gz.md5">MD5</a>]
+ </p>
+ </div>
+
+ <div class="section"><h3>TCK<a name="TCK"></a></h3>
+ <p>
+ This is a download for all implementors of JDO, and for those who want to check
+ how well an implementation is compliant with the JDO specification.
+ The tck2 project contains the JDO 2 Technology Compatibility Kit.
+ The source distribution is the only artifact needed to be downloaded
+ by the user. The dependencies (including the model20 jar,
+ util20 jar, enhancer20 jar, api2 jar, and JPOX)
+ are automatically downloaded by maven as needed to run the TCK.
+
+ </p>
+ <p>
+ <a href="[preferred]/db/jdo/3.0/jdo-tck-3.0-src.zip">jdo-tck-3.0-src.zip</a>
+ [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-tck-3.0-src.zip.asc">PGP</a>]
+ [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-tck-3.0-src.zip.md5">MD5</a>]
+ </p>
+ <p>
+ <a href="[preferred]/db/jdo/3.0/jdo-tck-3.0-src.tar.gz">jdo-tck-3.0-src.tar.gz</a>
+ [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-tck-3.0-src.tar.gz.asc">PGP</a>]
+ [<a class="externalLink" href="http://www.apache.org/dist/db/jdo/3.0/jdo-tck-3.0-src.tar.gz.md5">MD5</a>]
+ </p>
+ </div>
+
+ </div>
+
+<div class="section"><h2>Verifying Releases<a name="Verifying_Releases"></a></h2>
+<a name="Verifying"></a>
+<p>It is essential that you verify the integrity of the downloaded
+files using the PGP signature and/or the MD5 checksum. The
+checksum is not as strong an indicator as the PGP signature is.</p>
+<p>The PGP signatures can be verified using PGP or GPG.
+First download the <a class="externalLink" href="http://www.apache.org/dist/db/jdo/KEYS">KEYS</a>
+as well as the <tt>asc</tt> signature file for the particular
+distribution.
+Make sure you get these files from the
+<a class="externalLink" href="http://www.apache.org/dist/db/jdo/">main distribution
+directory</a>, rather than from a mirror. Then verify the signatures using
+</p>
+<p><tt>
+% pgpk -a KEYS<br />
+% pgpv <i>release_name</i>.tar.gz.asc<br />
+</tt>
+<i>or</i><br />
+<tt>
+% pgp -ka KEYS<br />
+% pgp <i>release_name</i>.tar.gz.asc<br />
+</tt>
+<i>or</i><br />
+<tt>
+% gpg --import KEYS<br />
+% gpg --verify <i>release_name</i>.tar.gz.asc
+</tt></p>
+<p>Alternatively, you can verify the checksums on the files. Unix
+programs called <tt>md5</tt>/<tt>sha1</tt> or
+<tt>md5sum</tt>/<tt>sha1sum</tt> are included in many unix
+distributions. <tt>*sum</tt> is also available as part of
+<a class="externalLink" href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>.
+Windows users can get binary md5 programs from <a class="externalLink" href="http://www.fourmilab.ch/md5/">http://www.fourmilab.ch/md5</a> and
+<a class="externalLink" href="http://www.pc-tools.net/win32/freeware/console/">hhttp://www.pc-tools.net/win32/freeware/console</a>.
+Windows SlavaSoft <a class="externalLink" href="http://www.slavasoft.com/fsum/">fsum</a> supports MD5 and
+SHA1.</p>
+<p>We highly recommend verifying the PGP signature, though.</p>
+ </div>
+
</div>
</div>
Modified: websites/production/db/content/jdo/roadmap.html
==============================================================================
--- websites/production/db/content/jdo/roadmap.html (original)
+++ websites/production/db/content/jdo/roadmap.html Mon Jan 21 04:23:17 2013
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 16, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 20, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Maven -
+ <title>JDO -
Project Roadmap</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -12,7 +12,7 @@
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
<meta name="author" content="JDO Documentation Team" />
- <meta name="Date-Revision-yyyymmdd" content="20130116" />
+ <meta name="Date-Revision-yyyymmdd" content="20130120" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,13 @@
<div id="breadcrumbs">
- <div class="xright"> <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
+ <div class="xright"> <a href="https://www.facebook.com/JavaDataObjects" class="externalLink" title="Facebook">Facebook</a>
+ |
+ <a href="https://twitter.com/JavaDataObjects" class="externalLink" title="Twitter">Twitter</a>
+ |
+ <a href="https://plus.google.com/106584233526334524963" class="externalLink" title="Google+">Google+</a>
+ |
+ <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
|
<a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630" class="externalLink" title="Issue Tracker">Issue Tracker</a>
|
@@ -204,36 +210,36 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License. -->
-
-
- <div class="section"><h2>Roadmap and TODO<a name="Roadmap_and_TODO"></a></h2>
-
- <p>
- The Apache JDO project has maintenance releases as part of its development cycle.
- See <a class="externalLink" href="https://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630">JIRA</a> for details of the planned and completed work.
- </p>
-
- <p>
- <a class="externalLink" href="mailto:jdo-dev@db.apache.org?subject=New Feature Idea">Submit an Idea</a>
- </p>
-
-</div>
-
-
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License. -->
+
+
+ <div class="section"><h2>Roadmap and TODO<a name="Roadmap_and_TODO"></a></h2>
+
+ <p>
+ The Apache JDO project has maintenance releases as part of its development cycle.
+ See <a class="externalLink" href="https://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630">JIRA</a> for details of the planned and completed work.
+ </p>
+
+ <p>
+ <a class="externalLink" href="mailto:jdo-dev@db.apache.org?subject=New Feature Idea">Submit an Idea</a>
+ </p>
+
+</div>
+
+
</div>
</div>
Modified: websites/production/db/content/jdo/specifications.html
==============================================================================
--- websites/production/db/content/jdo/specifications.html (original)
+++ websites/production/db/content/jdo/specifications.html Mon Jan 21 04:23:17 2013
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 16, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 20, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Maven -
+ <title>JDO -
Specifications</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -12,7 +12,7 @@
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
<meta name="author" content="JDO Documentation Team" />
- <meta name="Date-Revision-yyyymmdd" content="20130116" />
+ <meta name="Date-Revision-yyyymmdd" content="20130120" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,13 @@
<div id="breadcrumbs">
- <div class="xright"> <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
+ <div class="xright"> <a href="https://www.facebook.com/JavaDataObjects" class="externalLink" title="Facebook">Facebook</a>
+ |
+ <a href="https://twitter.com/JavaDataObjects" class="externalLink" title="Twitter">Twitter</a>
+ |
+ <a href="https://plus.google.com/106584233526334524963" class="externalLink" title="Google+">Google+</a>
+ |
+ <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
|
<a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630" class="externalLink" title="Issue Tracker">Issue Tracker</a>
|
@@ -204,45 +210,45 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License. -->
-
- <div class="section"><h2>JDO Final Specifications<a name="JDO_Final_Specifications"></a></h2>
- <p>
- The following specifications for JDO are available
- </p>
- <ul>
- <li>The <a class="externalLink" href="http://jcp.org/aboutJava/communityprocess/mrel/jsr243/index3.html">JDO 3.0 Specification (Maintenance Release 3)</a> </li>
- <li>The <a class="externalLink" href="http://jcp.org/aboutJava/communityprocess/mrel/jsr243/index2.html">JDO 2.2 Specification (Maintenance Release 2)</a> </li>
- <li>The <a class="externalLink" href="http://www.jcp.org/en/jsr/detail?id=243">JDO 2.1 Specification (Maintenance Release 1)</a></li>
- <li>The <a class="externalLink" href="http://www.jcp.org/en/jsr/detail?id=243">JDO 2.0 Specification (Final)</a></li>
- <li>The <a class="externalLink" href="http://www.jcp.org/en/jsr/detail?id=12">JDO 1.0 Specification (Final)</a></li>
- </ul>
- </div>
- <div class="section"><h2>JDO Draft Specifications<a name="JDO_Draft_Specifications"></a></h2>
- <p>
- The following specifications for JDO are snapshots of the current Maintenance
- Release specification under development. The specification has not been released.
- Additions and changes are underway. Send comments to
- <a class="externalLink" href="mailto:jdo-experts-ext@sun.com">jdo-experts-ext@sun.com</a>.
- </p>
- <ul>
- <li>None at this time </li>
- </ul>
- </div>
-
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License. -->
+
+ <div class="section"><h2>JDO Final Specifications<a name="JDO_Final_Specifications"></a></h2>
+ <p>
+ The following specifications for JDO are available
+ </p>
+ <ul>
+ <li>The <a class="externalLink" href="http://jcp.org/aboutJava/communityprocess/mrel/jsr243/index3.html">JDO 3.0 Specification (Maintenance Release 3)</a> </li>
+ <li>The <a class="externalLink" href="http://jcp.org/aboutJava/communityprocess/mrel/jsr243/index2.html">JDO 2.2 Specification (Maintenance Release 2)</a> </li>
+ <li>The <a class="externalLink" href="http://www.jcp.org/en/jsr/detail?id=243">JDO 2.1 Specification (Maintenance Release 1)</a></li>
+ <li>The <a class="externalLink" href="http://www.jcp.org/en/jsr/detail?id=243">JDO 2.0 Specification (Final)</a></li>
+ <li>The <a class="externalLink" href="http://www.jcp.org/en/jsr/detail?id=12">JDO 1.0 Specification (Final)</a></li>
+ </ul>
+ </div>
+ <div class="section"><h2>JDO Draft Specifications<a name="JDO_Draft_Specifications"></a></h2>
+ <p>
+ The following specifications for JDO are snapshots of the current Maintenance
+ Release specification under development. The specification has not been released.
+ Additions and changes are underway. Send comments to
+ <a class="externalLink" href="mailto:jdo-experts-ext@sun.com">jdo-experts-ext@sun.com</a>.
+ </p>
+ <ul>
+ <li>None at this time </li>
+ </ul>
+ </div>
+
</div>
</div>
Modified: websites/production/db/content/jdo/state_transition.html
==============================================================================
--- websites/production/db/content/jdo/state_transition.html (original)
+++ websites/production/db/content/jdo/state_transition.html Mon Jan 21 04:23:17 2013
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 16, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 20, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Maven -
+ <title>JDO -
JDO State Transitions</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -11,7 +11,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20130116" />
+ <meta name="Date-Revision-yyyymmdd" content="20130120" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -30,7 +30,13 @@
<div id="breadcrumbs">
- <div class="xright"> <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
+ <div class="xright"> <a href="https://www.facebook.com/JavaDataObjects" class="externalLink" title="Facebook">Facebook</a>
+ |
+ <a href="https://twitter.com/JavaDataObjects" class="externalLink" title="Twitter">Twitter</a>
+ |
+ <a href="https://plus.google.com/106584233526334524963" class="externalLink" title="Google+">Google+</a>
+ |
+ <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
|
<a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630" class="externalLink" title="Issue Tracker">Issue Tracker</a>
|
@@ -203,183 +209,183 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
-
-
- <div class="section"><h2>JDO State Transition<a name="JDO_State_Transition"></a></h2>
- <p>
- JDO manages the lifecycle of an object, from creation (<b>Transient</b>) through to persistence in the datastore (<b>Hollow</b>, <b>Persistent Clean</b>) and all of the various states between these. The transition between these states are achieved by using methods on the Persistence Manager such as <i>makePersistent()</i>, <i>makeTransient()</i>, <i>deletePersistent()</i>, and by commiting the changes made by these operations, or by rolling them back.
- </p>
- <p>
- The various lifecycle states supported by JDO are shown below.
- </p>
- <table border="0" class="bodyTable">
- <tr class="a">
- <th>Name</th>
- <th>Description</th>
- </tr>
- <tr class="b">
- <td>Transient</td>
- <td>Any object created by the developer that do are not persisted. These don't have a JDO identity.</td>
- </tr>
- <tr class="a">
- <td>Persistent New</td>
- <td>Any object that is newly persisted in the current transaction. A JDO identity has been assigned to these objects.</td>
- </tr>
- <tr class="b">
- <td>Persistent Dirty</td>
- <td>Any persistent object that has been changed in the current transaction.</td>
- </tr>
- <tr class="a">
- <td>Hollow</td>
- <td>Any persistent object that represents data in the datastore, but whose values are not in the instance.</td>
- </tr>
- <tr class="b">
- <td>Persistent Clean</td>
- <td>Any persistent object that represents data in the datastore, and whose values have not been changed in the current transaction.</td>
- </tr>
- <tr class="a">
- <td>Persistent Deleted</td>
- <td>Any persistent object that represents data in the datastore, and that has been deleted in the current transaction.</td>
- </tr>
- <tr class="b">
- <td>Persistent New Deleted</td>
- <td>Any object that have been newly made persistent and then deleted in the same current transaction.</td>
- </tr>
- <tr class="a">
- <td>Persistent Non transactional</td>
- <td>Any persistent object that represents data in the datastore, whose values are loaded but not transactionally consistent.</td>
- </tr>
- <tr class="b">
- <td>Persistent Non transactional Dirty</td>
- <td>Any persistent object that represents data in the datastore, whose values are loaded but not transactionally consistent, and that has been modified.</td>
- </tr>
- <tr class="a">
- <td>Transient Clean</td>
- <td>Any transient object that represents a transactional instance whose values have not been changed in the current transaction.</td>
- </tr>
- <tr class="b">
- <td>Transient Dirty</td>
- <td>Any transient object that represents a transactional instance whose values have been changed in the current transaction.</td>
- </tr>
- <tr class="a">
- <td>Detached Clean</td>
- <td>Any detached object that represents a persistent instance whose values have not been changed since detaching.</td>
- </tr>
- <tr class="b">
- <td>Detached Dirty</td>
- <td>Any detached object that represents a persistent instance whose values have been changed since detaching.</td>
- </tr>
- </table>
-
- <div class="section"><h3>Detecting Object State<a name="Detecting_Object_State"></a></h3>
- <p>
- JDO provides a class <a href="jdohelper.html">JDOHelper</a> that allows you to interrogate the object state via its attributes (isPersistent(), isDeleted(), etc).
- In JDO 2.1 for JDKs 1.5+ <i>JDOHelper</i> is extended to also provide a method that gives the full object state.
- </p>
- <div class="source"><pre>ObjectState state = JDOHelper.getObjectState(obj);</pre></div>
- <br />
- </div>
-
- <div class="section"><h3>Persisting an object<a name="Persisting_an_object"></a></h3>
- <p>
- The most basic thing you can do with JDO is persist an object. The following code is an example of how you can do this
- </p>
- <div class="source"><pre>
-Transaction tx=pm.currentTransaction();
-try
-{
- tx.begin();
- Product product = new Product("Plate", 9.99);
- pm.makePersistent(product);
- tx.commit();
-}
-finally
-{
- if (tx.isActive())
- {
- tx.rollback();
- }
-}
- </pre></div>
- <p>
- The <i>Product</i> object progresses from <b>Transient</b> (initial, unpersisted state), through to <b>Persistent New</b>, and then finally to <b>Hollow</b> when it reaches the data store (after the "commit"). If the persist failed, it would "rollback" and hence end up in the same state as when it started. The following diagram shows this graphically
- </p>
- <br />
- <img src="images/state_transition_persist.gif" alt="" />
- <br />
- </div>
-
- <div class="section"><h3>Updating an object<a name="Updating_an_object"></a></h3>
- <p>
- When you have persisted objects you need to update them. The following code is an example of how you can do this
- </p>
- <div class="source"><pre>
-Transaction tx=pm.currentTransaction();
-try
-{
- tx.begin();
- String product_name = product.getName();
- ...
- product.setPrice(7.50);
- tx.commit();
-}
-finally
-{
- if (tx.isActive())
- {
- tx.rollback();
- }
-}
- </pre></div>
- <p>
- The <i>Product</i> object starts off in <b>Hollow</b> state and progresses to <b>Persistent Clean</b> when the user requires to read from it. It then migrates to <b>Persistent Dirty</b> when the price is updated. Finally it returns to <b>Hollow</b> when the user commits/rolls back the transaction. The following diagram shows this graphically
- </p>
- <br />
- <img src="images/state_transition_update.gif" alt="" />
- <br />
- </div>
-
- <div class="section"><h3>Deleting an object<a name="Deleting_an_object"></a></h3>
- <p>
- When you no longer need an object persisted, you can delete it. The following code is an example of how you can do this
- </p>
- <div class="source"><pre>
-Transaction tx=pm.currentTransaction();
-try
-{
- tx.begin();
- String product_name = product.getName();
- ...
- pm.deletePersistent(product);
- tx.commit();
-}
-finally
-{
- if (tx.isActive())
- {
- tx.rollback();
- }
-}
- </pre></div>
- <p>
- The <i>Product</i> object starts off in <b>Hollow</b> state and progresses to <b>Persistent Clean</b> when the user requires to read from it. It then migrates to <b>Persistent Deleted</b> when the deletePersistent() called. Finally it either progresses to <b>Transient</b> when commit is called, or returns to <b>Hollow</b> if it is rolled back. The following diagram shows this graphically
- </p>
- <br />
- <img src="images/state_transition_delete.gif" alt="" />
- <br />
- </div>
-
- <div class="section"><h3>Possible state transitions<a name="Possible_state_transitions"></a></h3>
- <p>
- The following diagram shows the state transitions possible with JDO.
- </p>
- <br />
- <img src="images/state_transition.gif" border="0" alt="JDO State Transition" />
- <br />
- </div>
- </div>
-
-
+
+
+ <div class="section"><h2>JDO State Transition<a name="JDO_State_Transition"></a></h2>
+ <p>
+ JDO manages the lifecycle of an object, from creation (<b>Transient</b>) through to persistence in the datastore (<b>Hollow</b>, <b>Persistent Clean</b>) and all of the various states between these. The transition between these states are achieved by using methods on the Persistence Manager such as <i>makePersistent()</i>, <i>makeTransient()</i>, <i>deletePersistent()</i>, and by commiting the changes made by these operations, or by rolling them back.
+ </p>
+ <p>
+ The various lifecycle states supported by JDO are shown below.
+ </p>
+ <table border="0" class="bodyTable">
+ <tr class="a">
+ <th>Name</th>
+ <th>Description</th>
+ </tr>
+ <tr class="b">
+ <td>Transient</td>
+ <td>Any object created by the developer that do are not persisted. These don't have a JDO identity.</td>
+ </tr>
+ <tr class="a">
+ <td>Persistent New</td>
+ <td>Any object that is newly persisted in the current transaction. A JDO identity has been assigned to these objects.</td>
+ </tr>
+ <tr class="b">
+ <td>Persistent Dirty</td>
+ <td>Any persistent object that has been changed in the current transaction.</td>
+ </tr>
+ <tr class="a">
+ <td>Hollow</td>
+ <td>Any persistent object that represents data in the datastore, but whose values are not in the instance.</td>
+ </tr>
+ <tr class="b">
+ <td>Persistent Clean</td>
+ <td>Any persistent object that represents data in the datastore, and whose values have not been changed in the current transaction.</td>
+ </tr>
+ <tr class="a">
+ <td>Persistent Deleted</td>
+ <td>Any persistent object that represents data in the datastore, and that has been deleted in the current transaction.</td>
+ </tr>
+ <tr class="b">
+ <td>Persistent New Deleted</td>
+ <td>Any object that have been newly made persistent and then deleted in the same current transaction.</td>
+ </tr>
+ <tr class="a">
+ <td>Persistent Non transactional</td>
+ <td>Any persistent object that represents data in the datastore, whose values are loaded but not transactionally consistent.</td>
+ </tr>
+ <tr class="b">
+ <td>Persistent Non transactional Dirty</td>
+ <td>Any persistent object that represents data in the datastore, whose values are loaded but not transactionally consistent, and that has been modified.</td>
+ </tr>
+ <tr class="a">
+ <td>Transient Clean</td>
+ <td>Any transient object that represents a transactional instance whose values have not been changed in the current transaction.</td>
+ </tr>
+ <tr class="b">
+ <td>Transient Dirty</td>
+ <td>Any transient object that represents a transactional instance whose values have been changed in the current transaction.</td>
+ </tr>
+ <tr class="a">
+ <td>Detached Clean</td>
+ <td>Any detached object that represents a persistent instance whose values have not been changed since detaching.</td>
+ </tr>
+ <tr class="b">
+ <td>Detached Dirty</td>
+ <td>Any detached object that represents a persistent instance whose values have been changed since detaching.</td>
+ </tr>
+ </table>
+
+ <div class="section"><h3>Detecting Object State<a name="Detecting_Object_State"></a></h3>
+ <p>
+ JDO provides a class <a href="jdohelper.html">JDOHelper</a> that allows you to interrogate the object state via its attributes (isPersistent(), isDeleted(), etc).
+ In JDO 2.1 for JDKs 1.5+ <i>JDOHelper</i> is extended to also provide a method that gives the full object state.
+ </p>
+ <div class="source"><pre>ObjectState state = JDOHelper.getObjectState(obj);</pre></div>
+ <br />
+ </div>
+
+ <div class="section"><h3>Persisting an object<a name="Persisting_an_object"></a></h3>
+ <p>
+ The most basic thing you can do with JDO is persist an object. The following code is an example of how you can do this
+ </p>
+ <div class="source"><pre>
+Transaction tx=pm.currentTransaction();
+try
+{
+ tx.begin();
+ Product product = new Product("Plate", 9.99);
+ pm.makePersistent(product);
+ tx.commit();
+}
+finally
+{
+ if (tx.isActive())
+ {
+ tx.rollback();
+ }
+}
+ </pre></div>
+ <p>
+ The <i>Product</i> object progresses from <b>Transient</b> (initial, unpersisted state), through to <b>Persistent New</b>, and then finally to <b>Hollow</b> when it reaches the data store (after the "commit"). If the persist failed, it would "rollback" and hence end up in the same state as when it started. The following diagram shows this graphically
+ </p>
+ <br />
+ <img src="images/state_transition_persist.gif" alt="" />
+ <br />
+ </div>
+
+ <div class="section"><h3>Updating an object<a name="Updating_an_object"></a></h3>
+ <p>
+ When you have persisted objects you need to update them. The following code is an example of how you can do this
+ </p>
+ <div class="source"><pre>
+Transaction tx=pm.currentTransaction();
+try
+{
+ tx.begin();
+ String product_name = product.getName();
+ ...
+ product.setPrice(7.50);
+ tx.commit();
+}
+finally
+{
+ if (tx.isActive())
+ {
+ tx.rollback();
+ }
+}
+ </pre></div>
+ <p>
+ The <i>Product</i> object starts off in <b>Hollow</b> state and progresses to <b>Persistent Clean</b> when the user requires to read from it. It then migrates to <b>Persistent Dirty</b> when the price is updated. Finally it returns to <b>Hollow</b> when the user commits/rolls back the transaction. The following diagram shows this graphically
+ </p>
+ <br />
+ <img src="images/state_transition_update.gif" alt="" />
+ <br />
+ </div>
+
+ <div class="section"><h3>Deleting an object<a name="Deleting_an_object"></a></h3>
+ <p>
+ When you no longer need an object persisted, you can delete it. The following code is an example of how you can do this
+ </p>
+ <div class="source"><pre>
+Transaction tx=pm.currentTransaction();
+try
+{
+ tx.begin();
+ String product_name = product.getName();
+ ...
+ pm.deletePersistent(product);
+ tx.commit();
+}
+finally
+{
+ if (tx.isActive())
+ {
+ tx.rollback();
+ }
+}
+ </pre></div>
+ <p>
+ The <i>Product</i> object starts off in <b>Hollow</b> state and progresses to <b>Persistent Clean</b> when the user requires to read from it. It then migrates to <b>Persistent Deleted</b> when the deletePersistent() called. Finally it either progresses to <b>Transient</b> when commit is called, or returns to <b>Hollow</b> if it is rolled back. The following diagram shows this graphically
+ </p>
+ <br />
+ <img src="images/state_transition_delete.gif" alt="" />
+ <br />
+ </div>
+
+ <div class="section"><h3>Possible state transitions<a name="Possible_state_transitions"></a></h3>
+ <p>
+ The following diagram shows the state transitions possible with JDO.
+ </p>
+ <br />
+ <img src="images/state_transition.gif" border="0" alt="JDO State Transition" />
+ <br />
+ </div>
+ </div>
+
+
</div>
</div>
Modified: websites/production/db/content/jdo/svn.html
==============================================================================
--- websites/production/db/content/jdo/svn.html (original)
+++ websites/production/db/content/jdo/svn.html Mon Jan 21 04:23:17 2013
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 16, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 20, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Maven -
+ <title>JDO -
Source Code</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -12,7 +12,7 @@
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
<meta name="author" content="JDO Documentation Team" />
- <meta name="Date-Revision-yyyymmdd" content="20130116" />
+ <meta name="Date-Revision-yyyymmdd" content="20130120" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,13 @@
<div id="breadcrumbs">
- <div class="xright"> <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
+ <div class="xright"> <a href="https://www.facebook.com/JavaDataObjects" class="externalLink" title="Facebook">Facebook</a>
+ |
+ <a href="https://twitter.com/JavaDataObjects" class="externalLink" title="Twitter">Twitter</a>
+ |
+ <a href="https://plus.google.com/106584233526334524963" class="externalLink" title="Google+">Google+</a>
+ |
+ <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
|
<a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630" class="externalLink" title="Issue Tracker">Issue Tracker</a>
|
@@ -204,179 +210,179 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License. -->
-
-
-
-<div class="section"><h2>Source Code Version Control<a name="Source_Code_Version_Control"></a></h2>
-
-<p>Apache JDO uses <a class="external" href="http://subversion.tigris.org" rel="nofollow">Subversion</a> to manage its source code.
-If you're new to Subversion, you can check out the
-<a class="externalLink" href="http://svnbook.red-bean.com/">online book</a> about Subversion.
-Note that we are currently using Subversion 1.1.x (there are separate
-versions of the book covering 1.0 and 1.1).
-</p>
-<p>
-To receive notice of commits to the repository subscribe to <a class="externalLink" href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a class="externalLink" href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
-
-</div>
-
-<div class="section"><h2>Web Access to Subversion<a name="Web_Access_to_Subversion"></a></h2>
-
-<p>
-If you just want to browse the source code, you can use the
-<a class="external" href="http://svn.apache.org/viewcvs/db/jdo" rel="nofollow">
-ViewCVS web interface</a> to Subversion. This is current at all times.
-</p>
-
-</div>
-
-<div class="section"><h2>Checking Out Code Using Subversion<a name="Checking_Out_Code_Using_Subversion"></a></h2>
-
-<p>Anyone can check code out of Subversion. You only need to specify a
-username and password to update the Subversion repository, and only
-JDO committers can do that.
-If you are a committer, are working from behind a firewall, or are connected to the internet through a proxy server, please see the sections below for more information.</p>
-
-<div class="section"><h3>Anonymous check out from Subversion<a name="Anonymous_check_out_from_Subversion"></a></h3>
-<p>Use a command like:</p>
-<div><pre>% svn checkout http://svn.apache.org/repos/asf/db/jdo </pre></div>
-<p>Once you have Apache JDO checked out you can update the source by executing the following command from within the jdo. </p>
-<div><pre>
-% svn update
-</pre></div>
-</div>
-<div class="section"><h3>Access from behind a firewall<a name="Access_from_behind_a_firewall"></a></h3>
-
-<p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
-<div><pre>
-% svn checkout https://svn.apache.org/repos/asf/db/jdo
-</pre></div>
-
-</div>
-<div class="section"><h3>Access through a proxy<a name="Access_through_a_proxy"></a></h3>
-
-<p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.) </p>
-<p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
-<p>Example : Edit the 'servers' file and add something like : </p>
-<div><pre>
-[global]
-http-proxy-host = your.proxy.name
-http-proxy-port = 3128
-</pre></div>
-<p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
-
-</div>
-
-<div class="section"><h3>Committer access<a name="Committer_access"></a></h3>
-
-<p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
-<div><pre>
-% svn checkout https://svn.apache.org/repos/asf/db/jdo
-</pre></div>
-</div>
-<div class="section"><h3>NetBeans CVS repository access<a name="NetBeans_CVS_repository_access"></a></h3>
-
-<p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a class="external" href="http://www.netbeans.org/community/sources" rel="nofollow">NetBeans sources</a> page for more info. </p>
-<p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
-</div>
-</div>
-
-<div class="section"><h2>Submitting Code Changes<a name="Submitting_Code_Changes"></a></h2>
-<div class="section"><h3>Submitting a patch<a name="Submitting_a_patch"></a></h3>
-
-<p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a class="externalLink" href="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</a>. To create a patch, simply execute the following command: </p>
-<div><pre>
-% svn diff > your-changes.patch
-</pre></div>
-</div>
-
-<div class="section"><h3>Committing changes to subversion<a name="Committing_changes_to_subversion"></a></h3>
-<p>
-To commit changes to the Subversion repository, you must be an Apache JDO committer. See <a href="get-involved.html">Get Involved</a> for information on how to become a committer and how to set up your password once you become a committer.
-</p>
-
-<p>
-Once your password is set, you can use a command like this to commit:
-</p>
-<div><pre>
-$> svn commit --username your-username
-Authentication realm: <https://svn.apache.org:443> ASF Committers
-Password for 'your-username': your-password
-</pre></div>
-<p>You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command). Here is the command if you are Windows or a single user unix computer: </p>
-<div><pre>
-$> svn commit --username your-username --password your-password
-</pre></div>
-<p>Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org. </p>
-
-</div>
-</div>
-
-<div class="section"><h2>Building JDO from Source<a name="Building_JDO_from_Source"></a></h2>
-<p>Refer to the <a class="externalLink" href="http://wiki.apache.org/jdo/FrontPage">Wiki
-page</a> for details. Note that the JDO project is subdivided into several
-smaller projects, and each project is built separately. </p>
-
-</div>
-
-<div class="section"><h2>Using Subversion on Windows with cygwin<a name="Using_Subversion_on_Windows_with_cygwin"></a></h2>
-
-<p>If you use Subversion on Windows under cygwin, you may find that the Subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <i>svn diff</i> of the file:
-</p>
-<div><pre>
-Property changes on: test/sql/derby/datastoreidentity/schema1.sql
-___________________________________________________________________
-Name: svn:executable
- + *
-</pre></div>
-<p>This section explains the source of the problem and suggests some actions to avoid it. </p>
-
-<div class="section"><h3>Background<a name="Background"></a></h3>
-
-<p>Subversion carries executable information in the built-in property called svn:executable. This property, unlike others, may be present or absent, but it has no value. You can add it or delete it, but but you cannot change its value. </p>
-<p>In theory, Subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
-<p>If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke <i>svn add</i>. </p>
-</div>
-<div class="section"><h3>Removing existing executable properties from the repository<a name="Removing_existing_executable_properties_from_the_repository"></a></h3>
-
-<p>You can use svn propdel to remove the svn:executable property from your working copy.
-</p>
-<div><pre>
- svn propdel -R svn:executable .
-</pre></div>
-<p>will recursively remove the svn:executable property from all of the files below the current directory. You can use this and commit the files to clean the repository if necessary. </p>
-
-</div>
-<div class="section"><h3>Preventing Subversion from adding unwanted executable properties<a name="Preventing_Subversion_from_adding_unwanted_executable_properties"></a></h3>
-
-<p>Windows/cygwin users who don't want to have to think about using <i>svn propdel</i> or <i>chmod</i> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a class="externalLink" href="http://subversion.tigris.org/project_packages.html" rel="nofollow">http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation add the svn.exe location to your Windows PATH variable. If you are switching from cygwin svn to Win32 svn </p>
-<ol style="list-style-type: decimal">
-<li><p>Remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. (In the Select Packages window of the setup wizard, navigate to the subversion package in the Devel. category. Click on the status icon until Uninstall is displayed. Click next and continue through the wizard until installation is complete.) </p>
-
-</li>
-<li><p>Copy the servers file and the auth folder from the sygwin ~/.subversion directory to C:\Documents and Settings\<user>\Application Data\Subversion used by Win32 subversion. </p>
-</li>
-</ol>
-<p>Note that windows svn uses backslash as the path separator when displaying file names. You cannot just copy and paste this file name to another svn command when running from within a cygwin shell. You need to enclose the file name into double quotes. </p>
-<p>Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder & select Properties. Select the Security tab. Click Advanced. Remove all instances of Read & Execute from the Permission Entries. Click "Reset permissions on all child objects and enable propogations of inheritable permissions". Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory. </p>
-
-</div>
-</div>
-
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License. -->
+
+
+
+<div class="section"><h2>Source Code Version Control<a name="Source_Code_Version_Control"></a></h2>
+
+<p>Apache JDO uses <a class="external" href="http://subversion.tigris.org" rel="nofollow">Subversion</a> to manage its source code.
+If you're new to Subversion, you can check out the
+<a class="externalLink" href="http://svnbook.red-bean.com/">online book</a> about Subversion.
+Note that we are currently using Subversion 1.1.x (there are separate
+versions of the book covering 1.0 and 1.1).
+</p>
+<p>
+To receive notice of commits to the repository subscribe to <a class="externalLink" href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a class="externalLink" href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
+
+</div>
+
+<div class="section"><h2>Web Access to Subversion<a name="Web_Access_to_Subversion"></a></h2>
+
+<p>
+If you just want to browse the source code, you can use the
+<a class="external" href="http://svn.apache.org/viewcvs/db/jdo" rel="nofollow">
+ViewCVS web interface</a> to Subversion. This is current at all times.
+</p>
+
+</div>
+
+<div class="section"><h2>Checking Out Code Using Subversion<a name="Checking_Out_Code_Using_Subversion"></a></h2>
+
+<p>Anyone can check code out of Subversion. You only need to specify a
+username and password to update the Subversion repository, and only
+JDO committers can do that.
+If you are a committer, are working from behind a firewall, or are connected to the internet through a proxy server, please see the sections below for more information.</p>
+
+<div class="section"><h3>Anonymous check out from Subversion<a name="Anonymous_check_out_from_Subversion"></a></h3>
+<p>Use a command like:</p>
+<div><pre>% svn checkout http://svn.apache.org/repos/asf/db/jdo </pre></div>
+<p>Once you have Apache JDO checked out you can update the source by executing the following command from within the jdo. </p>
+<div><pre>
+% svn update
+</pre></div>
+</div>
+<div class="section"><h3>Access from behind a firewall<a name="Access_from_behind_a_firewall"></a></h3>
+
+<p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
+<div><pre>
+% svn checkout https://svn.apache.org/repos/asf/db/jdo
+</pre></div>
+
+</div>
+<div class="section"><h3>Access through a proxy<a name="Access_through_a_proxy"></a></h3>
+
+<p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.) </p>
+<p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
+<p>Example : Edit the 'servers' file and add something like : </p>
+<div><pre>
+[global]
+http-proxy-host = your.proxy.name
+http-proxy-port = 3128
+</pre></div>
+<p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
+
+</div>
+
+<div class="section"><h3>Committer access<a name="Committer_access"></a></h3>
+
+<p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
+<div><pre>
+% svn checkout https://svn.apache.org/repos/asf/db/jdo
+</pre></div>
+</div>
+<div class="section"><h3>NetBeans CVS repository access<a name="NetBeans_CVS_repository_access"></a></h3>
+
+<p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a class="external" href="http://www.netbeans.org/community/sources" rel="nofollow">NetBeans sources</a> page for more info. </p>
+<p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
+</div>
+</div>
+
+<div class="section"><h2>Submitting Code Changes<a name="Submitting_Code_Changes"></a></h2>
+<div class="section"><h3>Submitting a patch<a name="Submitting_a_patch"></a></h3>
+
+<p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a class="externalLink" href="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</a>. To create a patch, simply execute the following command: </p>
+<div><pre>
+% svn diff > your-changes.patch
+</pre></div>
+</div>
+
+<div class="section"><h3>Committing changes to subversion<a name="Committing_changes_to_subversion"></a></h3>
+<p>
+To commit changes to the Subversion repository, you must be an Apache JDO committer. See <a href="get-involved.html">Get Involved</a> for information on how to become a committer and how to set up your password once you become a committer.
+</p>
+
+<p>
+Once your password is set, you can use a command like this to commit:
+</p>
+<div><pre>
+$> svn commit --username your-username
+Authentication realm: <https://svn.apache.org:443> ASF Committers
+Password for 'your-username': your-password
+</pre></div>
+<p>You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command). Here is the command if you are Windows or a single user unix computer: </p>
+<div><pre>
+$> svn commit --username your-username --password your-password
+</pre></div>
+<p>Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org. </p>
+
+</div>
+</div>
+
+<div class="section"><h2>Building JDO from Source<a name="Building_JDO_from_Source"></a></h2>
+<p>Refer to the <a class="externalLink" href="http://wiki.apache.org/jdo/FrontPage">Wiki
+page</a> for details. Note that the JDO project is subdivided into several
+smaller projects, and each project is built separately. </p>
+
+</div>
+
+<div class="section"><h2>Using Subversion on Windows with cygwin<a name="Using_Subversion_on_Windows_with_cygwin"></a></h2>
+
+<p>If you use Subversion on Windows under cygwin, you may find that the Subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <i>svn diff</i> of the file:
+</p>
+<div><pre>
+Property changes on: test/sql/derby/datastoreidentity/schema1.sql
+___________________________________________________________________
+Name: svn:executable
+ + *
+</pre></div>
+<p>This section explains the source of the problem and suggests some actions to avoid it. </p>
+
+<div class="section"><h3>Background<a name="Background"></a></h3>
+
+<p>Subversion carries executable information in the built-in property called svn:executable. This property, unlike others, may be present or absent, but it has no value. You can add it or delete it, but but you cannot change its value. </p>
+<p>In theory, Subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
+<p>If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke <i>svn add</i>. </p>
+</div>
+<div class="section"><h3>Removing existing executable properties from the repository<a name="Removing_existing_executable_properties_from_the_repository"></a></h3>
+
+<p>You can use svn propdel to remove the svn:executable property from your working copy.
+</p>
+<div><pre>
+ svn propdel -R svn:executable .
+</pre></div>
+<p>will recursively remove the svn:executable property from all of the files below the current directory. You can use this and commit the files to clean the repository if necessary. </p>
+
+</div>
+<div class="section"><h3>Preventing Subversion from adding unwanted executable properties<a name="Preventing_Subversion_from_adding_unwanted_executable_properties"></a></h3>
+
+<p>Windows/cygwin users who don't want to have to think about using <i>svn propdel</i> or <i>chmod</i> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a class="externalLink" href="http://subversion.tigris.org/project_packages.html" rel="nofollow">http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation add the svn.exe location to your Windows PATH variable. If you are switching from cygwin svn to Win32 svn </p>
+<ol style="list-style-type: decimal">
+<li><p>Remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. (In the Select Packages window of the setup wizard, navigate to the subversion package in the Devel. category. Click on the status icon until Uninstall is displayed. Click next and continue through the wizard until installation is complete.) </p>
+
+</li>
+<li><p>Copy the servers file and the auth folder from the sygwin ~/.subversion directory to C:\Documents and Settings\<user>\Application Data\Subversion used by Win32 subversion. </p>
+</li>
+</ol>
+<p>Note that windows svn uses backslash as the path separator when displaying file names. You cannot just copy and paste this file name to another svn command when running from within a cygwin shell. You need to enclose the file name into double quotes. </p>
+<p>Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder & select Properties. Select the Security tab. Click Advanced. Remove all instances of Read & Execute from the Permission Entries. Click "Reset permissions on all child objects and enable propogations of inheritable permissions". Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory. </p>
+
+</div>
+</div>
+
</div>
</div>
Modified: websites/production/db/content/jdo/tck.html
==============================================================================
--- websites/production/db/content/jdo/tck.html (original)
+++ websites/production/db/content/jdo/tck.html Mon Jan 21 04:23:17 2013
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 16, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 20, 2013 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Maven -
+ <title>JDO -
TCK</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -12,7 +12,7 @@
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
<meta name="author" content="JDO Documentation Team" />
- <meta name="Date-Revision-yyyymmdd" content="20130116" />
+ <meta name="Date-Revision-yyyymmdd" content="20130120" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -31,7 +31,13 @@
<div id="breadcrumbs">
- <div class="xright"> <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
+ <div class="xright"> <a href="https://www.facebook.com/JavaDataObjects" class="externalLink" title="Facebook">Facebook</a>
+ |
+ <a href="https://twitter.com/JavaDataObjects" class="externalLink" title="Twitter">Twitter</a>
+ |
+ <a href="https://plus.google.com/106584233526334524963" class="externalLink" title="Google+">Google+</a>
+ |
+ <a href="http://wiki.apache.org/jdo" class="externalLink" title="Wiki">Wiki</a>
|
<a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630" class="externalLink" title="Issue Tracker">Issue Tracker</a>
|
@@ -204,63 +210,63 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License. -->
-
-
-
-<div class="section"><h2>About the Technology Compatibility Kit<a name="About_the_Technology_Compatibility_Kit"></a></h2>
-
-<p>
- In order to demonstrate compliance with the Java Data Objects specification,
- an implementation must pass all of the tests in the Technology Compatibility Kit (TCK).
- The TCK is released as a packaged Java source tree.
- Maven is the driver of a test run. You must download and install
- <a class="externalLink" href="http://maven.apache.org/">Maven 2+</a>before running the TCK.
-</p>
-</div>
-
-<div class="section"><h2>Running the TCK<a name="Running_the_TCK"></a></h2>
- <p>
- To run the Technology Compatibility Kit:
- </p>
- <ol style="list-style-type: decimal">
- <li>
- Check out the JDO source code from the most recent branch. See <a class="externalLink" href="http://db.apache.org/jdo/svn.html">Source Code</a> for instructions on checking out code.
- </li>
- <li>
- Follow the instructions in the Prerequisites section of
- <a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/*checkout*/db/jdo/branches/2.3-ea/README.html">README.html</a>.
- </li>
- <li>
- Follow the procedure in <a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/*checkout*/db/jdo/branches/2.3-ea/tck2/RunRules.html">RunRules.html</a> in the jdo2-tck-<i>version</i> directory.
- </li>
- </ol>
-</div>
-
-<div class="section"><h2>Demonstrating Compliance<a name="Demonstrating_Compliance"></a></h2>
-<p>
-Vendors must post test results 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
-configuration information and test results. For an example of the
-required posting, please see <a href="tck/final">http://db.apache.org/jdo/tck/final</a>.
-</p>
-</div>
-
-
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License. -->
+
+
+
+<div class="section"><h2>About the Technology Compatibility Kit<a name="About_the_Technology_Compatibility_Kit"></a></h2>
+
+<p>
+ In order to demonstrate compliance with the Java Data Objects specification,
+ an implementation must pass all of the tests in the Technology Compatibility Kit (TCK).
+ The TCK is released as a packaged Java source tree.
+ Maven is the driver of a test run. You must download and install
+ <a class="externalLink" href="http://maven.apache.org/">Maven 2+</a>before running the TCK.
+</p>
+</div>
+
+<div class="section"><h2>Running the TCK<a name="Running_the_TCK"></a></h2>
+ <p>
+ To run the Technology Compatibility Kit:
+ </p>
+ <ol style="list-style-type: decimal">
+ <li>
+ Check out the JDO source code from the most recent branch. See <a class="externalLink" href="http://db.apache.org/jdo/svn.html">Source Code</a> for instructions on checking out code.
+ </li>
+ <li>
+ Follow the instructions in the Prerequisites section of
+ <a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/*checkout*/db/jdo/branches/2.3-ea/README.html">README.html</a>.
+ </li>
+ <li>
+ Follow the procedure in <a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/*checkout*/db/jdo/branches/2.3-ea/tck2/RunRules.html">RunRules.html</a> in the jdo2-tck-<i>version</i> directory.
+ </li>
+ </ol>
+</div>
+
+<div class="section"><h2>Demonstrating Compliance<a name="Demonstrating_Compliance"></a></h2>
+<p>
+Vendors must post test results 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
+configuration information and test results. For an example of the
+required posting, please see <a href="tck/final">http://db.apache.org/jdo/tck/final</a>.
+</p>
+</div>
+
+
</div>
</div>