Regards Michael
There are currently 14 challenges filed by BEA that need to be
resolved within 15 working days of receipt.
From the TCK RunRules document that is part of the official JSR
release, the first level TCK Challenge process includes the following:
<spec>
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:
[email protected] <mailto:[email protected]> 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.
The Maintenance Lead will respond within 15 working days with a
decision on whether there is an error in the test case. If the issue
is found by the Maintenance Lead to be due to an error in the test
case, the Maintenance Lead might provide a patch that will be
included in the next maintenance revision. If the patch is not
provided within 15 working days of the receipt of the challenge,
then the test may be put into the TCK directory
src/conf/exclude.list and it will not be run as part of the TCK.
Decisions of the Maintenance Lead may be appealed to the full expert
group. A vote of the full expert group will be conducted by 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.
</spec>
I'd like to propose a process for handling the test case challenges.
I've created a branch
https://svn.apache.org/repos/asf/db/jdo/branches/2.0.1 into which we
can put the patches referenced by the process. This allows us to
manage patches that might differ from the trunk. This is necessary
in case we want to modify a test case because the specification is
unclear, but change the specification instead of changing the test
case.
A wiki page has been created to track the TCK challenges
http://wiki.apache.org/jdo/TCKChallenges?action=show which can be
updated by anyone. The JIRA that tracks each challenge is identified
here. Fixes that have already been committed to the trunk will be
merged into the 2.0.1 branch.
The challenger should check out the 2.0.1 branch and verify that the
fix as identified in the JIRA is ok. If there is an issue with the
fix, the JIRA should be updated with comments. If a resolution is
not acceptable by the challenger, then an appeal to the entire
expert group should be filed.
Comments?
Craig Russell
[EMAIL PROTECTED] http://db.apache.org/jdo
--Michael Bouschen [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED] http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Index: tck20/project.xml
===================================================================
--- tck20/project.xml (Revision 452257)
+++ tck20/project.xml (Arbeitskopie)
@@ -23,7 +23,7 @@
<name>JDO2 Technology Compatibility Kit</name>
<groupId>org.apache.jdo</groupId>
<artifactId>jdo2-tck</artifactId>
- <currentVersion>2.0</currentVersion>
+ <currentVersion>2.0.1</currentVersion>
<package>org.apache.jdo.tck</package>
<shortDescription>Java Data Objects 2.0 (JDO)
TCK</shortDescription>
<description>The Java Data Objects 2.0 (JDO) API is a standard
interface-based Java model abstraction of persistence, developed as
Java Specification Request JSR 243 under the auspices of the Java
Community Process.
@@ -39,39 +39,39 @@
<dependency>
<groupId>javax.jdo</groupId>
<artifactId>jdo2-api</artifactId>
- <version>2.0</version>
+ <version>2.0.1</version>
</dependency>
<dependency>
<groupId>org.apache.jdo</groupId>
<artifactId>jdo2-enhancer</artifactId>
- <version>2.0</version>
+ <version>2.0.1</version>
</dependency>
<dependency>
<groupId>org.apache.jdo</groupId>
<artifactId>jdo2-core</artifactId>
- <version>2.0</version>
+ <version>2.0.1</version>
</dependency>
<dependency>
<groupId>jpox</groupId>
<artifactId>jpox</artifactId>
- <version>1.1.0</version>
+ <version>1.1.1</version>
<url>http://www.jpox.org/docs/download.html</url>
</dependency>
<dependency>
<groupId>jpox</groupId>
<artifactId>jpox-enhancer</artifactId>
- <version>1.1.0</version>
+ <version>1.1.1</version>
<url>http://www.jpox.org/docs/download.html</url>
</dependency>
<dependency>
<groupId>org.apache.derby</groupId>
<artifactId>derby</artifactId>
- <version>10.1.1.0</version>
+ <version>10.1.3.1</version>
</dependency>
<dependency>
<groupId>org.apache.derby</groupId>
<artifactId>derbytools</artifactId>
- <version>10.1.1.0</version>
+ <version>10.1.3.1</version>
</dependency>
<dependency>
<groupId>junit</groupId>
@@ -113,13 +113,13 @@
<dependency>
<groupId>jpox</groupId>
<artifactId>jpox-c3p0</artifactId>
- <version>1.1.0</version>
+ <version>1.1.1</version>
<url>http://www.jpox.org/docs/download.html</url>
</dependency>
<dependency>
<groupId>jpox</groupId>
<artifactId>jpox-dbcp</artifactId>
- <version>1.1.0</version>
+ <version>1.1.1</version>
<url>http://www.jpox.org/docs/download.html</url>
</dependency>
<dependency>
Index: enhancer20/project.xml
===================================================================
--- enhancer20/project.xml (Revision 452257)
+++ enhancer20/project.xml (Arbeitskopie)
@@ -25,7 +25,7 @@
<name>JDO2 Implementation (Enhancer)</name>
<groupId>org.apache.jdo</groupId>
<artifactId>jdo2-enhancer</artifactId>
- <currentVersion>2.0</currentVersion>
+ <currentVersion>2.0.1</currentVersion>
<package>org.apache.jdo</package>
<shortDescription>Java Data Objects 2.0 (JDO)
Enhancer</shortDescription>
<description>The Java Data Objects 2.0 (JDO) API is a standard
interface-based
@@ -39,12 +39,12 @@
<dependency>
<groupId>javax.jdo</groupId>
<artifactId>jdo2-api</artifactId>
- <version>2.0</version>
+ <version>2.0.1</version>
</dependency>
<dependency>
<groupId>org.apache.jdo</groupId>
<artifactId>jdo2-core</artifactId>
- <version>2.0</version>
+ <version>2.0.1</version>
</dependency>
<dependency>
<id>commons-logging</id>
Index: project.xml
===================================================================
--- project.xml (Revision 452257)
+++ project.xml (Arbeitskopie)
@@ -112,7 +112,7 @@
<id>ebengtson</id>
<email>[EMAIL PROTECTED]</email>
<timezone>1</timezone>
- <organization>Sun Micrsystems</organization>
+ <organization>JPOX</organization>
</developer>
<developer>
<name>Geir Magnusson, Jr.</name>
Index: core20/project.xml
===================================================================
--- core20/project.xml (Revision 452257)
+++ core20/project.xml (Arbeitskopie)
@@ -25,7 +25,7 @@
<name>JDO2 Implementation (Core)</name>
<groupId>org.apache.jdo</groupId>
<artifactId>jdo2-core</artifactId>
- <currentVersion>2.0</currentVersion>
+ <currentVersion>2.0.1</currentVersion>
<package>org.apache.jdo</package>
<shortDescription>Java Data Objects 2.0 (JDO)
Core</shortDescription>
<description>The Java Data Objects 2.0 (JDO) API is a standard
interface-based
Index: api20/project.xml
===================================================================
--- api20/project.xml (Revision 452257)
+++ api20/project.xml (Arbeitskopie)
@@ -24,7 +24,7 @@
<name>JDO2 API</name>
<groupId>javax.jdo</groupId>
<artifactId>jdo2-api</artifactId>
- <currentVersion>2.0</currentVersion>
+ <currentVersion>2.0.1</currentVersion>
<package>javax.jdo</package>
<shortDescription>Java Data Objects 2.0 (JDO)
API</shortDescription>
<description>The Java Data Objects 2.0 (JDO) API is a standard
interface-based
