openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r858693 - in /websites/staging/openjpa/trunk/content: ./ running-the-sun-tck-for-jpa.html
Date Tue, 16 Apr 2013 15:49:01 GMT
Author: buildbot
Date: Tue Apr 16 15:49:01 2013
New Revision: 858693

Staging update by buildbot for openjpa

    websites/staging/openjpa/trunk/content/   (props changed)

Propchange: websites/staging/openjpa/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 16 15:49:01 2013
@@ -1 +1 @@

Modified: websites/staging/openjpa/trunk/content/running-the-sun-tck-for-jpa.html
--- websites/staging/openjpa/trunk/content/running-the-sun-tck-for-jpa.html (original)
+++ websites/staging/openjpa/trunk/content/running-the-sun-tck-for-jpa.html Tue Apr 16 15:49:01
@@ -174,6 +174,19 @@ committers (other TCKs are available to 
 <p>More information on running the TCK can be found in the <a href="">pom.xml
file for the tck module</a> and the corresponding <a href="">ant
script for the current tck</a>.</p>
+<h2 id="what-to-do-with-a-new-revision-of-the-tck">What to do with a new revision of
the TCK</h2>
+<p>Periodically, the TCK is updated by Oracle.  This may be a maintenance release,
or it may be due to a new release of the JPA specification.
+In either case, there are a few steps that need to be performed to recognize and execute
this updated TCK test bucket.</p>
+<li>Create an xml file specific to the updated TCK.  The name is based off the TCK
level and date of the release.
+The easiest way is to copy an existing version (ie. tck2-20110815.xml).</li>
+<li>Update this entry in the newly created xml file to point at the downloaded TCK
zip file name:<br>
+&lt; property name="tck.level" value="jpatck-2.0_15-Aug-2011" \&gt;</li>
+<li>Update the openjpa-integration/tck/pom.xml by modifying this entry appropriately:<br>
+&lt; tck2.level >20110815&lt; /tck2.level&gt;</li>
+<li>You may also need to create a new tckx-profile, if it's required for a new release
of the specification.  I'll leave that as an exercise for
+the next editor...</li>

View raw message