[jira] Commented: (JDO-299) Signature test needed checking compliance of implementations with JDO2.0 API

[ http://issues.apache.org/jira/browse/JDO-299?page=comments#action_12370708 ] Craig Russell commented on JDO-299: --- Looks good. Go ahead and check it in. Signature test needed checking compliance of implementations with JDO2.0 API

[jira] Updated: (JDO-341) Discrepancies between: JDO2.0 spec v. API20 v. SignatureTest's descriptor file

[ http://issues.apache.org/jira/browse/JDO-341?page=all ] Martin Zaun updated JDO-341: Attachment: features_in_signature_descriptor_but_not_in_jdo20_spec.txt Discrepancies between: JDO2.0 spec v. API20 v. SignatureTest's descriptor file

[jira] Commented: (JDO-309) minor extensions to tck20 test utilities

[ http://issues.apache.org/jira/browse/JDO-309?page=comments#action_12370744 ] Martin Zaun commented on JDO-309: - Removed executable property from new file RogueBarrier.java with revision 386446. minor extensions to tck20 test utilities

[jira] Commented: (JDO-299) Signature test needed checking compliance of implementations with JDO2.0 API

[ http://issues.apache.org/jira/browse/JDO-299?page=comments#action_12370746 ] Martin Zaun commented on JDO-299: - Created issue JDO-341 for fixing the found discrepancies between: JDO2.0 spec v. API20 v. SignatureTest's descriptor file. Signature test

[jira] Resolved: (JDO-299) Signature test needed checking compliance of implementations with JDO2.0 API

[ http://issues.apache.org/jira/browse/JDO-299?page=all ] Martin Zaun resolved JDO-299: - Resolution: Fixed Committed the signature test with revision 386448. Signature test needed checking compliance of implementations with JDO2.0 API

Javadoc warning with api20 interface FetchPlan

Hi, when building the api20 project using JDK1.4 I get a javadoc warning from the FetchPlan interface. You find the warning in the attached text file. I propose to change the javadoc comment to avoid the warning. You my proposed change in the patch file. Regards Michael -- Michael Bouschen

[jira] Resolved: (JDO-259) Write tests for new persistent-nontransactional-dirty behavior assertions

[ http://issues.apache.org/jira/browse/JDO-259?page=all ] Craig Russell resolved JDO-259: --- Resolution: Fixed svn commit -m JDO-259 Added new NontransactionalWrite tests; removed the old test

[jira] Commented: (JDO-299) Signature test needed checking compliance of implementations with JDO2.0 API

[ http://issues.apache.org/jira/browse/JDO-299?page=comments#action_12370774 ] Martin Zaun commented on JDO-299: - I noticed that the SignatureTest does not get run as part of the maven runtck.jdori goal. So, I've added signatures.conf to the

JDO TCK Conference Call Friday, Mar 17, 9 am PST

Hi, We will have our regular meeting Friday, March 17 at 9 am PST to discuss JDO TCK issues and status. Dial-in numbers are: 866 230-6968 294-0479# International: +1 865 544-7856 Agenda: 1. Test status (Michael) 2. New tests status (Martin, Michael, Craig) 3. JSR 243 next steps (Craig) 4.

[jira] Commented: (JDO-341) Discrepancies between: JDO2.0 spec v. API20 v. SignatureTest's descriptor file

[ http://issues.apache.org/jira/browse/JDO-341?page=comments#action_12370776 ] Craig Russell commented on JDO-341: --- For issue 1, class ObjectIdentity: public static java.lang.String STRING_DELIMITER; This has been changed to have private access.