db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <craig.russ...@oracle.com>
Subject Minutes: JDO TCK Conference Call Friday, Feb 17, 9 am Pacific Time
Date Fri, 17 Feb 2012 17:58:41 GMT
Attendees: Michael Bouschen, Michelle Caisse, Matthew Adams, Craig  


  1. JDO 3.0.1 release status

Done and done.

  2. News on retire JDO Expert Group mail list?

The expert group mail list will be retired. Everyone who wants to  
continue on the project should join the jdo-dev mailing list. Send a  
message to jdo-dev-subscribe@db.apache.org.

  3. Delete maven1 config files: https://issues.apache.org/jira/browse/JDO-705 

Ok to go. AI Michael look at the files in the trunk, including making  
sure that the README is correct.

On a related note, anything left on "Run TCK using Maven2 for  
consistency"?  https://issues.apache.org/jira/browse/JDO-647.

Doing mvn install on the tck, there is still an open issue with  
missing logger information. AI Michelle open a new JIRA.

  4. News on new feature idea http://osdir.com/ml/jdo-dev-db-apache/2011-11/msg00002.html

  - possible code contribution from 3M?

no news.

  5. Everyone please review the ChangeLog: http://wiki.apache.org/jdo/ChangeLog

Good feedback on the change log. Thanks, Andy.

Items on the PROPOSED list that are already in 3.0. AI Michelle move  
12, 13, 14, 15, 16, 17 to ACCEPTED, and move ACCEPTED 7 to the same  
block of changes.

  6. News on JDO-696 "Throw on unrecognized javax.jdo options"? See https://issues.apache.org/jira/browse/JDO-696

no news.

  7. What's needed to release 3.1? Go to https://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630

      click "Issues" in the menu on the left and then click "JDO 3  
maintenacnce release 1 (3.1)" under "Unresolved: By Version"

  8. Other issues

JDO-682 sequences are not supported for Derby with DataNucleus. The  
SQL for Derby is "NEXT VALUE FOR sequenceName".

Superclass that is not persistence capable. Don't want to persist the  
superclass but need to declare the fields as persistent in the  
superclass. May be able to define the superclass as persistence  
capable but not map it to the database.

  Action Items from weeks past:

  [April 8 2011] AI Craig comment on https://issues.apache.org/jira/browse/JDO-617 
  re the utility of the update operator.
  [Sep 23 2011] AI Michael document when changing dependencies (to  
DataNucleus) it's necessary to rebuild the exectck project before  
running tck.

Craig L Russell
Architect, Oracle
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

View raw message