Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Craig Russell

  Agenda:

1. Delete maven1 config files: https://issues.apache.org/jira/browse/JDO-705 . Check README.html. Reason for JDO3.MF under trunk?

Two items left.

README.html needs to be reviewed.

The JDO3.MF is not needed any more. The new mvn build process makes this obsolete.

2. News on new feature idea http://osdir.com/ml/jdo-dev-db-apache/2011-11/msg00002.html - possible code contribution from 3M?

no change.

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

The ChangeLog was updated. Thanks, Michelle and Michael.

  4. No enhancer log output with maven 2: 
https://issues.apache.org/jira/browse/JDO-706

May be a class path issue. AI Michelle update the JIRA with some info on how to get more diagnostics. Where does log4j find its config file? May have to put the config file there.

5. 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"

For JDO-682 the patch for sequences has been put into DataNucleus. We need to update DataNucleus dependencies. Currently using DataNucleus 3.0.6 but the fix is in DataNucleus 3.0.8.

  6. Other issues

The specification is now in svn under trunk/specification. This is where the spec will be updated. The version was last updated in July 7, 2011. Anyone with access to FrameMaker can try to build the jdo.book. The jdo.book needs to be updated to refer to the jdo.fm instead of jdo-2011-07-07.fm.

  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
http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!

Reply via email to