Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. JDO 2.2 release issues. All tests pass in the branch except the signature test for api2-legacy. Still need to debug this. Planning to roll the release today. This might be the last release of api2-legacy unless we find someone in the community willing to own it. Volunteers?

2. Use of class loaders in api2 JDO config tests. The patch that Richard put together (thanks!) doesn't completely explain the usage of the URL ClassLoader. The class loader that the tests need don't have a parent so the loader only can load data supplied by the test case, not any TCK test classes. So it's not sufficient for the purpose of actually getting a PMF implementation as needed by some new api2 tests. More work is needed for the new tests. AI Matthew: take a look at the patch and clarify the "unparent" parameter for the JDOConfigTestClassLoader. AI Craig: comment on the patch.

3. JDO 2.3 planning: We have a list of features for JDO 2.3. Will discuss in future conference calls.

4. Other issues

Richard's javadoc issue. No one else can reproduce this. Perhaps a clean install would be the best course of action.

Action Items from weeks past:

[Feb 1 2008] AI Matthew see what would be needed to update the PMF contract to support ServiceLoader. Done.

[Nov 30 2007] AI Christiaan propose more details on Update/copy by query for post-JDO 2.1.

[May 25 2007] AI everyone download the Grails demo from grails.org and check it out. Also look at Grails/Groovy ExpandoMetaClass that has the magic to avoid reflection and enhancement.

[May 25 2007] AI Matthew Adams prepare a proposal with just the basics of schema synchronization with jdo and orm metadata.

[Sep 2 2005] AI: To recruit members: Articles on TheServerSide directing attention to the site. T-shirts. AI: Craig write a ServerSide article.

-- Michelle

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to